Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e37e852a23a35b28dc8c50049f49e41b572356e5c5285cb0fed972e1c522c30c

Tx prefix hash: 3c24e46fa549c2c430ba869121f91c0ab04fbb95cd93913774dc1c140fa740e4
Tx public key: 67ecbc2a95e88ca0cba5f878af29a5ea0100f31b2d0b093dfbf2f20ad0cee450
Timestamp: 1701660438 Timestamp [UCT]: 2023-12-04 03:27:18 Age [y:d:h:m:s]: 01:159:07:46:38
Block: 905505 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375049 RingCT/type: yes/0
Extra: 0167ecbc2a95e88ca0cba5f878af29a5ea0100f31b2d0b093dfbf2f20ad0cee450021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.613318433000 dcy

stealth address amount amount idx
00: c2df11d9463685e49fb1e3d60d45822819a14fb0c5d6c3f24a84faf4c17d85e3 0.613318433000 1362394 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": 905515, "vin": [ { "gen": { "height": 905505 } } ], "vout": [ { "amount": 613318433, "target": { "key": "c2df11d9463685e49fb1e3d60d45822819a14fb0c5d6c3f24a84faf4c17d85e3" } } ], "extra": [ 1, 103, 236, 188, 42, 149, 232, 140, 160, 203, 165, 248, 120, 175, 41, 165, 234, 1, 0, 243, 27, 45, 11, 9, 61, 251, 242, 242, 10, 208, 206, 228, 80, 2, 17, 0, 0, 0, 5, 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