Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 923633a714f65e4aec5ca4375bec44d156b0ba51865747ccfb9a583996eb1262

Tx prefix hash: dfef57a5cbf89c20f99d423fcf97d6b14bbd3396cd5597726e341528ba92d6e6
Tx public key: a0ef55482b32c1b6e4702daf8f8fa06041e4478f7cb376043aca5eaf21886378
Timestamp: 1581244758 Timestamp [UCT]: 2020-02-09 10:39:18 Age [y:d:h:m:s]: 04:294:13:28:52
Block: 61243 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1102655 RingCT/type: yes/0
Extra: 01a0ef55482b32c1b6e4702daf8f8fa06041e4478f7cb376043aca5eaf2188637802110000000c8a2ee0d9000000000000000000

1 output(s) for total of 384.666911970000 dcy

stealth address amount amount idx
00: 3e2198ee3f8a0038306b88b8004e96da2cf7ac999344b287b5c16753f3bce2ea 384.666911970000 112859 of 0

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": 61253, "vin": [ { "gen": { "height": 61243 } } ], "vout": [ { "amount": 384666911970, "target": { "key": "3e2198ee3f8a0038306b88b8004e96da2cf7ac999344b287b5c16753f3bce2ea" } } ], "extra": [ 1, 160, 239, 85, 72, 43, 50, 193, 182, 228, 112, 45, 175, 143, 143, 160, 96, 65, 228, 71, 143, 124, 179, 118, 4, 58, 202, 94, 175, 33, 136, 99, 120, 2, 17, 0, 0, 0, 12, 138, 46, 224, 217, 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