Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ff97f879ec6623494cee7ece4b1d83a528aa2f4ae96aedb7a4fec96527f9083

Tx prefix hash: 09b3eca3c0fd492bb84541cc513ba871797cfa043b8e2ca4381ca8a1d7cbfb1e
Tx public key: 62e32f8c5920a1fc8edd9bc789cf6dd35ffa9a4b3a77b56be26cfed160d36411
Timestamp: 1714409431 Timestamp [UCT]: 2024-04-29 16:50:31 Age [y:d:h:m:s]: 01:192:14:11:28
Block: 1011206 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396277 RingCT/type: yes/0
Extra: 0162e32f8c5920a1fc8edd9bc789cf6dd35ffa9a4b3a77b56be26cfed160d3641102110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea5a9ec45a69f28e222d8d69a2ae91822f2cb247c9ef2a50882165f2998f4da2 0.600000000000 1473374 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": 1011216, "vin": [ { "gen": { "height": 1011206 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea5a9ec45a69f28e222d8d69a2ae91822f2cb247c9ef2a50882165f2998f4da2" } } ], "extra": [ 1, 98, 227, 47, 140, 89, 32, 161, 252, 142, 221, 155, 199, 137, 207, 109, 211, 95, 250, 154, 75, 58, 119, 181, 107, 226, 108, 254, 209, 96, 211, 100, 17, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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