Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4a04db1ced051620517b5de005067ee6126e16ad6732fa86f3ea76abcfbd32d

Tx prefix hash: ba11b8fa593e8fd540201829c0f6f06a86c0e325988c76409035e2e3af0d2690
Tx public key: c72be4cb0ef34123c0b0ad1845284f466e0d6531ed0da6e9edd7edac48253027
Timestamp: 1700489510 Timestamp [UCT]: 2023-11-20 14:11:50 Age [y:d:h:m:s]: 01:159:00:50:32
Block: 895799 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374859 RingCT/type: yes/0
Extra: 01c72be4cb0ef34123c0b0ad1845284f466e0d6531ed0da6e9edd7edac48253027021100000009e6d27f9c000000000000000000

1 output(s) for total of 0.660459268000 dcy

stealth address amount amount idx
00: 475677d3cb7e9db7a71a1dd364f727b57afa738e4fe3f96fadba98b8374cbe55 0.660459268000 1352046 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": 895809, "vin": [ { "gen": { "height": 895799 } } ], "vout": [ { "amount": 660459268, "target": { "key": "475677d3cb7e9db7a71a1dd364f727b57afa738e4fe3f96fadba98b8374cbe55" } } ], "extra": [ 1, 199, 43, 228, 203, 14, 243, 65, 35, 192, 176, 173, 24, 69, 40, 79, 70, 110, 13, 101, 49, 237, 13, 166, 233, 237, 215, 237, 172, 72, 37, 48, 39, 2, 17, 0, 0, 0, 9, 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