Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 655e86537ac32517cdf3cef060d9297f6ee3f995e59403e936a20ede05cc17db

Tx prefix hash: 361cf325f2d501f64a0f2aa8f2a17c3553013e89bd0ac51df0d02c107b6808cf
Tx public key: 0ae3e7eb3a4b4a096d82cd2b4ad27d3e920e4d6008d68f8da3baed351b0ea7e3
Timestamp: 1708144672 Timestamp [UCT]: 2024-02-17 04:37:52 Age [y:d:h:m:s]: 01:039:10:42:26
Block: 959266 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289214 RingCT/type: yes/0
Extra: 010ae3e7eb3a4b4a096d82cd2b4ad27d3e920e4d6008d68f8da3baed351b0ea7e302110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8530a09b0067d4413c0781141b28f66acc2eeb5f23767ee5cf7e61a1926c90d4 0.600000000000 1418797 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": 959276, "vin": [ { "gen": { "height": 959266 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8530a09b0067d4413c0781141b28f66acc2eeb5f23767ee5cf7e61a1926c90d4" } } ], "extra": [ 1, 10, 227, 231, 235, 58, 75, 74, 9, 109, 130, 205, 43, 74, 210, 125, 62, 146, 14, 77, 96, 8, 214, 143, 141, 163, 186, 237, 53, 27, 14, 167, 227, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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