Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7ae14e3174f381e3096028eef67486fdcde066107c0fd46da8da1fedebd8209

Tx prefix hash: 7c948f7700dd20cdd80075a830cd3e9eaf699b22b0c42c04dcbbccee25731992
Tx public key: 537ec7e6f0e399391830c1fb829b38d9919a8548ef18c2612efe9e5cf31a5b79
Timestamp: 1731091968 Timestamp [UCT]: 2024-11-08 18:52:48 Age [y:d:h:m:s]: 00:152:03:47:16
Block: 1149429 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108572 RingCT/type: yes/0
Extra: 01537ec7e6f0e399391830c1fb829b38d9919a8548ef18c2612efe9e5cf31a5b79021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ca6fd8cf3a164fa3acc89be32e11ddd02250f45eed5dee5848cbf6aaf0cfbcee 0.600000000000 1634504 of 15

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": 1149439, "vin": [ { "gen": { "height": 1149429 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ca6fd8cf3a164fa3acc89be32e11ddd02250f45eed5dee5848cbf6aaf0cfbcee" } } ], "extra": [ 1, 83, 126, 199, 230, 240, 227, 153, 57, 24, 48, 193, 251, 130, 155, 56, 217, 145, 154, 133, 72, 239, 24, 194, 97, 46, 254, 158, 92, 243, 26, 91, 121, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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