Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8793a83e60a0530a892d48a9e2e6c7285c60394a6b13f0904395040571445352

Tx prefix hash: 9b383a7a3d510677e362bc073c5b8f2b23d156f337f2d09fb1fe6bcd8551b169
Tx public key: 67be1cae6a0f3acac12f08f835754e8c96a9ebbb0bba1835cd90831d4d389ca5
Timestamp: 1737148184 Timestamp [UCT]: 2025-01-17 21:09:44 Age [y:d:h:m:s]: 00:151:21:26:59
Block: 1199572 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108255 RingCT/type: yes/0
Extra: 0167be1cae6a0f3acac12f08f835754e8c96a9ebbb0bba1835cd90831d4d389ca50211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 250a900404f48c87aa31ce96e27c0f28c7da54faa3fdc3aaca94bcc113b7ca4a 0.600000000000 1686203 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": 1199582, "vin": [ { "gen": { "height": 1199572 } } ], "vout": [ { "amount": 600000000, "target": { "key": "250a900404f48c87aa31ce96e27c0f28c7da54faa3fdc3aaca94bcc113b7ca4a" } } ], "extra": [ 1, 103, 190, 28, 174, 106, 15, 58, 202, 193, 47, 8, 248, 53, 117, 78, 140, 150, 169, 235, 187, 11, 186, 24, 53, 205, 144, 131, 29, 77, 56, 156, 165, 2, 17, 0, 0, 0, 5, 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