Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0d808efb39a8d77a6c3e9b95340ec9f594fc0c7e2714f14ad8c12f49a90231f

Tx prefix hash: 1bc0e9b2d99b96d9e173a9cb4055db56fbe9cf6dc1a9965ccaa9403cfc3bb508
Tx public key: f5e153c2b11621e620169618b37ea800b896c1749008dae68601e9a1d296f6b3
Timestamp: 1714981115 Timestamp [UCT]: 2024-05-06 07:38:35 Age [y:d:h:m:s]: 00:292:21:08:36
Block: 1015947 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209315 RingCT/type: yes/0
Extra: 01f5e153c2b11621e620169618b37ea800b896c1749008dae68601e9a1d296f6b30211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a6976f9947f36f2181a5e2c1a5dea147d1b1be8e5a5b6a041561255c79917a2 0.600000000000 1479390 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": 1015957, "vin": [ { "gen": { "height": 1015947 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a6976f9947f36f2181a5e2c1a5dea147d1b1be8e5a5b6a041561255c79917a2" } } ], "extra": [ 1, 245, 225, 83, 194, 177, 22, 33, 230, 32, 22, 150, 24, 179, 126, 168, 0, 184, 150, 193, 116, 144, 8, 218, 230, 134, 1, 233, 161, 210, 150, 246, 179, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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