Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 45aaef7b7ea4bc40542c84153c1b5ef5dc355cfe08423d2a67e63adccd3167c2

Tx prefix hash: ff2cc4bb03ce6a273116de2257ee7dfed7fe1ff9d0e43bcbf31319c784e5f3e1
Tx public key: cde7f2159cbe3a4552d7360751d925ba4a34f201f927ed3590afd1878726f0c3
Timestamp: 1686970014 Timestamp [UCT]: 2023-06-17 02:46:54 Age [y:d:h:m:s]: 01:213:10:53:37
Block: 783967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 413952 RingCT/type: yes/0
Extra: 01cde7f2159cbe3a4552d7360751d925ba4a34f201f927ed3590afd1878726f0c3021100000004e6d27f9c000000000000000000

1 output(s) for total of 1.550215383000 dcy

stealth address amount amount idx
00: 7f462b37456277bd4ccd41c0412b8ed4ffb05269c2e361cf89400d06489bc895 1.550215383000 1233842 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 783977, "vin": [ { "gen": { "height": 783967 } } ], "vout": [ { "amount": 1550215383, "target": { "key": "7f462b37456277bd4ccd41c0412b8ed4ffb05269c2e361cf89400d06489bc895" } } ], "extra": [ 1, 205, 231, 242, 21, 156, 190, 58, 69, 82, 215, 54, 7, 81, 217, 37, 186, 74, 52, 242, 1, 249, 39, 237, 53, 144, 175, 209, 135, 135, 38, 240, 195, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8