Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4f18da2faa17c68465a5bc879fe37559a4ea64cc7d2e80d176b7d566cf59011

Tx prefix hash: e57d698e4e66cc41228870d4b293ef05fbea2650e556f4f605acc856170ba0d6
Tx public key: ddabc2f10ecab1578fb7d43c26afa64fa8d322c2e383862e51d413d3e7a9af18
Timestamp: 1578475589 Timestamp [UCT]: 2020-01-08 09:26:29 Age [y:d:h:m:s]: 05:089:06:36:51
Block: 41098 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1213846 RingCT/type: yes/0
Extra: 01ddabc2f10ecab1578fb7d43c26afa64fa8d322c2e383862e51d413d3e7a9af1802110000009617786bcf000000000000000000

1 output(s) for total of 448.565751286000 dcy

stealth address amount amount idx
00: b1e9077256742fc1eaf8c94d2967e0e010a506a2a73dddc500639a98f3277dc6 448.565751286000 72864 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": 41108, "vin": [ { "gen": { "height": 41098 } } ], "vout": [ { "amount": 448565751286, "target": { "key": "b1e9077256742fc1eaf8c94d2967e0e010a506a2a73dddc500639a98f3277dc6" } } ], "extra": [ 1, 221, 171, 194, 241, 14, 202, 177, 87, 143, 183, 212, 60, 38, 175, 166, 79, 168, 211, 34, 194, 227, 131, 134, 46, 81, 212, 19, 211, 231, 169, 175, 24, 2, 17, 0, 0, 0, 150, 23, 120, 107, 207, 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