Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6483ee281d48ced3ab08681177d05542f9469a62a98a5bc6e9df8cc45a388d4

Tx prefix hash: 337f16d578ab63ae7d2f6160f9765470df4717bacf31061ad7b06d1876780134
Tx public key: cbe343fbb05c3c3f05273a70fb8523736d0bab6fafdaa3c960f9795ecdb948c2
Timestamp: 1734353598 Timestamp [UCT]: 2024-12-16 12:53:18 Age [y:d:h:m:s]: 00:093:09:12:33
Block: 1176464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66531 RingCT/type: yes/0
Extra: 01cbe343fbb05c3c3f05273a70fb8523736d0bab6fafdaa3c960f9795ecdb948c2021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf8ee7bd4b27564f57ff33342cf51fb2c92f721fb7c73e83a5071a5114dc4a82 0.600000000000 1662797 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": 1176474, "vin": [ { "gen": { "height": 1176464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf8ee7bd4b27564f57ff33342cf51fb2c92f721fb7c73e83a5071a5114dc4a82" } } ], "extra": [ 1, 203, 227, 67, 251, 176, 92, 60, 63, 5, 39, 58, 112, 251, 133, 35, 115, 109, 11, 171, 111, 175, 218, 163, 201, 96, 249, 121, 94, 205, 185, 72, 194, 2, 17, 0, 0, 0, 3, 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