Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abb97f6300966b1807857b62619f7704e6d7200f6d690993dc03d8d2351f68e4

Tx prefix hash: 52a80f653fafea3ebd7abaf0afa1f1c560351b4b8d09f653395e36b4c99ca7c9
Tx public key: deede45aadfb5e018cf3f440a79ac1f84c7cfe379c6e5f522f312cb335f8585e
Timestamp: 1727784389 Timestamp [UCT]: 2024-10-01 12:06:29 Age [y:d:h:m:s]: 00:163:01:36:44
Block: 1122098 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116343 RingCT/type: yes/0
Extra: 01deede45aadfb5e018cf3f440a79ac1f84c7cfe379c6e5f522f312cb335f8585e02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c078e7922528c43c36eadcd11e36851d879e80066c5f1f759ccff54c3f96e360 0.600000000000 1604475 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": 1122108, "vin": [ { "gen": { "height": 1122098 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c078e7922528c43c36eadcd11e36851d879e80066c5f1f759ccff54c3f96e360" } } ], "extra": [ 1, 222, 237, 228, 90, 173, 251, 94, 1, 140, 243, 244, 64, 167, 154, 193, 248, 76, 124, 254, 55, 156, 110, 95, 82, 47, 49, 44, 179, 53, 248, 88, 94, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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