Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0dd7e5487018852bda1a8daa1ef08dd734207ca4448b181ffab97fdf2d07e21

Tx prefix hash: cc8cf5d97ab342f1d5821a20af5c71016406dddfb6dc50168d226ddcab1a9c1b
Tx public key: a8227ee542c5fbc716cf734f1dcf14b104a1c08289df89e0c4de6dd3927322f2
Timestamp: 1582482420 Timestamp [UCT]: 2020-02-23 18:27:00 Age [y:d:h:m:s]: 04:344:21:09:32
Block: 70952 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1138919 RingCT/type: yes/0
Extra: 01a8227ee542c5fbc716cf734f1dcf14b104a1c08289df89e0c4de6dd3927322f20211000000058a2ee0d9000000000000000000

1 output(s) for total of 357.196646333000 dcy

stealth address amount amount idx
00: a40c3276da78ece54ffa53ad48ff746d929e550086bcd22080c9ac5e00c5511f 357.196646333000 131135 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": 70962, "vin": [ { "gen": { "height": 70952 } } ], "vout": [ { "amount": 357196646333, "target": { "key": "a40c3276da78ece54ffa53ad48ff746d929e550086bcd22080c9ac5e00c5511f" } } ], "extra": [ 1, 168, 34, 126, 229, 66, 197, 251, 199, 22, 207, 115, 79, 29, 207, 20, 177, 4, 161, 192, 130, 137, 223, 137, 224, 196, 222, 109, 211, 146, 115, 34, 242, 2, 17, 0, 0, 0, 5, 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