Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07675c4a9a47f886c3b9fd1b5442ca8cb6501405d0fbdd72aaa8d121c8898603

Tx prefix hash: ec7c33399d6d1d7aa0a9c0223e88f1d6ea031db9df573be80eb89020f97e3842
Tx public key: f2ee0621db75d82ea187cbae45d764659c22cb3731168147c79e7d2cdc561c28
Timestamp: 1583801160 Timestamp [UCT]: 2020-03-10 00:46:00 Age [y:d:h:m:s]: 04:253:22:20:40
Block: 79563 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1076437 RingCT/type: yes/0
Extra: 01f2ee0621db75d82ea187cbae45d764659c22cb3731168147c79e7d2cdc561c28021100000002a08fd034000000000000000000

1 output(s) for total of 334.484150366000 dcy

stealth address amount amount idx
00: a38d574548ec7aa8caeaf347e2baccf6047eefeff4aabfc92b524ce21cdbc51e 334.484150366000 145583 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": 79573, "vin": [ { "gen": { "height": 79563 } } ], "vout": [ { "amount": 334484150366, "target": { "key": "a38d574548ec7aa8caeaf347e2baccf6047eefeff4aabfc92b524ce21cdbc51e" } } ], "extra": [ 1, 242, 238, 6, 33, 219, 117, 216, 46, 161, 135, 203, 174, 69, 215, 100, 101, 156, 34, 203, 55, 49, 22, 129, 71, 199, 158, 125, 44, 220, 86, 28, 40, 2, 17, 0, 0, 0, 2, 160, 143, 208, 52, 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