Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90a67322a1b9f03b34890afed9e3059ecbec50a8f245b70b46a8e91385fc4dbc

Tx prefix hash: b9b52ca36989fd44b35dfd902909302a39b63ab0456e9f0e5c81d44e1f5adc1a
Tx public key: 6bf4b57347f3b6725ab56d04497a0dc156d38da2ee116e523576d1d311f86904
Timestamp: 1712080158 Timestamp [UCT]: 2024-04-02 17:49:18 Age [y:d:h:m:s]: 01:216:20:42:55
Block: 991861 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 413691 RingCT/type: yes/0
Extra: 016bf4b57347f3b6725ab56d04497a0dc156d38da2ee116e523576d1d311f869040211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 032c6c9fb969f644e7b5a304efbbd9982839b5252c9aae794ca8107fb5c45787 0.600000000000 1452197 of 15

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": 991871, "vin": [ { "gen": { "height": 991861 } } ], "vout": [ { "amount": 600000000, "target": { "key": "032c6c9fb969f644e7b5a304efbbd9982839b5252c9aae794ca8107fb5c45787" } } ], "extra": [ 1, 107, 244, 181, 115, 71, 243, 182, 114, 90, 181, 109, 4, 73, 122, 13, 193, 86, 211, 141, 162, 238, 17, 110, 82, 53, 118, 209, 211, 17, 248, 105, 4, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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