Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c614e40f3c7abad897779f9cd503457b5f6e84fe04e8c74cbe7a503f63540a29

Tx prefix hash: f744d7549231b93280e25fa532126f52815302494839d9dcc3c2ec69e56a7983
Tx public key: 0e4f0a9bf0ddaedbc0bb3e96cf012ac0df903c1b7628b14140db37cc9c23ac27
Timestamp: 1726513400 Timestamp [UCT]: 2024-09-16 19:03:20 Age [y:d:h:m:s]: 00:233:22:32:49
Block: 1111552 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167034 RingCT/type: yes/0
Extra: 010e4f0a9bf0ddaedbc0bb3e96cf012ac0df903c1b7628b14140db37cc9c23ac27021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f735f7d668e255d579bfd028e3a78f92b38438509e9df6800ff5ba66f75c2fb9 0.600000000000 1590553 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": 1111562, "vin": [ { "gen": { "height": 1111552 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f735f7d668e255d579bfd028e3a78f92b38438509e9df6800ff5ba66f75c2fb9" } } ], "extra": [ 1, 14, 79, 10, 155, 240, 221, 174, 219, 192, 187, 62, 150, 207, 1, 42, 192, 223, 144, 60, 27, 118, 40, 177, 65, 64, 219, 55, 204, 156, 35, 172, 39, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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