Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8feecda19599b1630c10321025cc74cfa81fb0e459291aa03c67c5857ce33e5a

Tx prefix hash: d606bbfe361aaec2f1ed07e825f5eceb71aebf1bb96af5bb010192d1f480b9cb
Tx public key: b6460b0cfb3e53ce3f3bfc506f845614a6894dfcc7862e8d0eb2a0948b10a16d
Timestamp: 1737024897 Timestamp [UCT]: 2025-01-16 10:54:57 Age [y:d:h:m:s]: 00:152:07:37:47
Block: 1198547 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108570 RingCT/type: yes/0
Extra: 01b6460b0cfb3e53ce3f3bfc506f845614a6894dfcc7862e8d0eb2a0948b10a16d0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 186a6142b6a9eb9cda9022e29dda1101778b4402098a2629cf8c8743349f8572 0.600000000000 1685172 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": 1198557, "vin": [ { "gen": { "height": 1198547 } } ], "vout": [ { "amount": 600000000, "target": { "key": "186a6142b6a9eb9cda9022e29dda1101778b4402098a2629cf8c8743349f8572" } } ], "extra": [ 1, 182, 70, 11, 12, 251, 62, 83, 206, 63, 59, 252, 80, 111, 132, 86, 20, 166, 137, 77, 252, 199, 134, 46, 141, 14, 178, 160, 148, 139, 16, 161, 109, 2, 17, 0, 0, 0, 6, 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