Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e64f6ecbbc5a131713e69681777ee60a80ae67f48f9a3d22fbc4ad9acbabfaaa

Tx prefix hash: 4111bc1d835e40b665d19cea0db6089a284973d28d6f496e6704d6a3831fae74
Tx public key: e08d9b28d281b87381db50b20cd5ac44772bf5f0f0beffed66aaf6310b2a87f8
Timestamp: 1732188438 Timestamp [UCT]: 2024-11-21 11:27:18 Age [y:d:h:m:s]: 00:164:03:58:59
Block: 1158505 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117162 RingCT/type: yes/0
Extra: 01e08d9b28d281b87381db50b20cd5ac44772bf5f0f0beffed66aaf6310b2a87f8021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4facd8c1e94664111da7a8ff2bd09e1cda0a6b822a29f1500684b015c6b782a 0.600000000000 1644134 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": 1158515, "vin": [ { "gen": { "height": 1158505 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4facd8c1e94664111da7a8ff2bd09e1cda0a6b822a29f1500684b015c6b782a" } } ], "extra": [ 1, 224, 141, 155, 40, 210, 129, 184, 115, 129, 219, 80, 178, 12, 213, 172, 68, 119, 43, 245, 240, 240, 190, 255, 237, 102, 170, 246, 49, 11, 42, 135, 248, 2, 17, 0, 0, 0, 5, 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