Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d3351e4a96e00b2a942a94d1f176d7bc4e53db645bcdf952c0d386b41d3c11f

Tx prefix hash: 365e0db06b48badb0073abddac607efa52719033ebb627e5dc32c28fae8c0ac9
Tx public key: 8c07907b03bcb393a6064d71f9cdf5bfbf7beebb2d07b202918d9c8ca3d6841e
Timestamp: 1734976101 Timestamp [UCT]: 2024-12-23 17:48:21 Age [y:d:h:m:s]: 00:109:16:36:07
Block: 1181623 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78158 RingCT/type: yes/0
Extra: 018c07907b03bcb393a6064d71f9cdf5bfbf7beebb2d07b202918d9c8ca3d6841e0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 95fceb46822e77031c68e70b6a46fa53858063279fd6df400c36811d4596a18d 0.600000000000 1668048 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": 1181633, "vin": [ { "gen": { "height": 1181623 } } ], "vout": [ { "amount": 600000000, "target": { "key": "95fceb46822e77031c68e70b6a46fa53858063279fd6df400c36811d4596a18d" } } ], "extra": [ 1, 140, 7, 144, 123, 3, 188, 179, 147, 166, 6, 77, 113, 249, 205, 245, 191, 191, 123, 238, 187, 45, 7, 178, 2, 145, 141, 156, 140, 163, 214, 132, 30, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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