Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 256a80f257ad9785c7e8e77335a4a1af339f0fb3dbb9fb9d89e17ec66869a78b

Tx prefix hash: 292b78dd62a16210f5406a3389f33c2bca835ca9f2e259890b70cd8d32e5f67b
Tx public key: 7c6836d5350f1830f5acf0e08c9603c2e50315066d645c4bbe88dc1151076928
Timestamp: 1719597218 Timestamp [UCT]: 2024-06-28 17:53:38 Age [y:d:h:m:s]: 00:213:01:40:35
Block: 1054209 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152225 RingCT/type: yes/0
Extra: 017c6836d5350f1830f5acf0e08c9603c2e50315066d645c4bbe88dc11510769280211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13075ebe0d8760e558fbd0d0691b71dd27b3c9aa87b1b5e9d9bedbcb2780a3d2 0.600000000000 1524570 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": 1054219, "vin": [ { "gen": { "height": 1054209 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13075ebe0d8760e558fbd0d0691b71dd27b3c9aa87b1b5e9d9bedbcb2780a3d2" } } ], "extra": [ 1, 124, 104, 54, 213, 53, 15, 24, 48, 245, 172, 240, 224, 140, 150, 3, 194, 229, 3, 21, 6, 109, 100, 92, 75, 190, 136, 220, 17, 81, 7, 105, 40, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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