Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 389dab7ba4e60a23c1362e5ef1fb93e63a2d363331d5cd447c2d14beb399ec39

Tx prefix hash: 11f7fd832e09a0801d0a17d889a58fe27fe3e6c3fc93398c57aabc3156b10fa6
Tx public key: 66d0e2409a21c4610116229e05d417a37f7b21d58a3077889a4299d8f252f72a
Timestamp: 1583932363 Timestamp [UCT]: 2020-03-11 13:12:43 Age [y:d:h:m:s]: 04:291:04:54:38
Block: 80468 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1103279 RingCT/type: yes/0
Extra: 0166d0e2409a21c4610116229e05d417a37f7b21d58a3077889a4299d8f252f72a0211000000013b1b9791000000000000000000

1 output(s) for total of 332.197736368000 dcy

stealth address amount amount idx
00: e2c2fefa148657432b405d0bda3303a1726a37c1fa8a8d2a0aef0b0e02be48d6 332.197736368000 147264 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": 80478, "vin": [ { "gen": { "height": 80468 } } ], "vout": [ { "amount": 332197736368, "target": { "key": "e2c2fefa148657432b405d0bda3303a1726a37c1fa8a8d2a0aef0b0e02be48d6" } } ], "extra": [ 1, 102, 208, 226, 64, 154, 33, 196, 97, 1, 22, 34, 158, 5, 212, 23, 163, 127, 123, 33, 213, 138, 48, 119, 136, 154, 66, 153, 216, 242, 82, 247, 42, 2, 17, 0, 0, 0, 1, 59, 27, 151, 145, 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