Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c524dfb5536e44e6db95968ca88cf6eca1683873990ffb75a5b519c286b74a7

Tx prefix hash: 89d17f278af875b318211c3aa9e799b693fbddb3542d06254e245d0d4ae8a075
Tx public key: 1f92db79ee8759efd59e9e4d7fd8d86f9931ab95f8f95bc7eb4881c31ebaba93
Timestamp: 1716244893 Timestamp [UCT]: 2024-05-20 22:41:33 Age [y:d:h:m:s]: 01:000:18:14:18
Block: 1026428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261464 RingCT/type: yes/0
Extra: 011f92db79ee8759efd59e9e4d7fd8d86f9931ab95f8f95bc7eb4881c31ebaba930211000000050011055b000000000000000000

1 output(s) for total of 0.615600000000 dcy

stealth address amount amount idx
00: 63e92543c38118792c1e3ab30f710614d835450d987f88f8e32d88246533e6fe 0.615600000000 1493507 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": 1026438, "vin": [ { "gen": { "height": 1026428 } } ], "vout": [ { "amount": 615600000, "target": { "key": "63e92543c38118792c1e3ab30f710614d835450d987f88f8e32d88246533e6fe" } } ], "extra": [ 1, 31, 146, 219, 121, 238, 135, 89, 239, 213, 158, 158, 77, 127, 216, 216, 111, 153, 49, 171, 149, 248, 249, 91, 199, 235, 72, 129, 195, 30, 186, 186, 147, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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