Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c703eeae5c078ac855cbdfd972da7423ca5496a8c52bd7413e60a9f1ce1bb6fc

Tx prefix hash: 4b4cf174ddb2011805eb0fc0a1b39e5a87266f6d1fea03ef42ce524130f4f5cc
Tx public key: 0ef10520b86002bf0e2ecbbb94b7236f71c25f25f2328486c223c3920049364e
Timestamp: 1704259633 Timestamp [UCT]: 2024-01-03 05:27:13 Age [y:d:h:m:s]: 01:089:04:50:18
Block: 927043 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324864 RingCT/type: yes/0
Extra: 010ef10520b86002bf0e2ecbbb94b7236f71c25f25f2328486c223c3920049364e02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 03c93b6ab37c5174b792fc839d0c9a8f64f7ead1fdb85f3c92326e6e7aa45d78 0.600000000000 1384843 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": 927053, "vin": [ { "gen": { "height": 927043 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03c93b6ab37c5174b792fc839d0c9a8f64f7ead1fdb85f3c92326e6e7aa45d78" } } ], "extra": [ 1, 14, 241, 5, 32, 184, 96, 2, 191, 14, 46, 203, 187, 148, 183, 35, 111, 113, 194, 95, 37, 242, 50, 132, 134, 194, 35, 195, 146, 0, 73, 54, 78, 2, 17, 0, 0, 0, 2, 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