Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74c9e2c39cb70d02f18e8e521eeb682e454187fcabbc072aa2e5807dadb7ff03

Tx prefix hash: cba281179870d2093bee054d8a5ea7de6521c5fb7d004748646bc287f062fbb6
Tx public key: 1b8d1bf1b7072ce3236087d20f8af4c2f1b2e89b6fed944ab89ee9eee4e16e07
Timestamp: 1694633945 Timestamp [UCT]: 2023-09-13 19:39:05 Age [y:d:h:m:s]: 01:063:08:48:12
Block: 847446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306554 RingCT/type: yes/0
Extra: 011b8d1bf1b7072ce3236087d20f8af4c2f1b2e89b6fed944ab89ee9eee4e16e0702110000000375e3f0e9000000000000000000

1 output(s) for total of 0.955123808000 dcy

stealth address amount amount idx
00: d510a910b583c7f5ab3265f4b6264a289a912f841f6513b1aaeea68bcddbe58e 0.955123808000 1300970 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": 847456, "vin": [ { "gen": { "height": 847446 } } ], "vout": [ { "amount": 955123808, "target": { "key": "d510a910b583c7f5ab3265f4b6264a289a912f841f6513b1aaeea68bcddbe58e" } } ], "extra": [ 1, 27, 141, 27, 241, 183, 7, 44, 227, 35, 96, 135, 210, 15, 138, 244, 194, 241, 178, 232, 155, 111, 237, 148, 74, 184, 158, 233, 238, 228, 225, 110, 7, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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