Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a835339dbd8d42bad124f571cb3b7a1f733206ea2252aa2a6e2cca0ab524519

Tx prefix hash: 3229df9e981b14325c815157d0e7b39b3a45c24ae71f81f11dea07e3aa9688cf
Tx public key: ecf9d25efe43261d9525f42aac98e0a0ec765b8b9292f4add289f32583fdd57e
Timestamp: 1698639421 Timestamp [UCT]: 2023-10-30 04:17:01 Age [y:d:h:m:s]: 01:151:15:45:08
Block: 880676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369386 RingCT/type: yes/0
Extra: 01ecf9d25efe43261d9525f42aac98e0a0ec765b8b9292f4add289f32583fdd57e021100000005faf35c9c000000000000000000

1 output(s) for total of 0.741233156000 dcy

stealth address amount amount idx
00: 98064f2c7a61bc32e0c06790e5f2a1c2ddd7f437e7b43bab97f37bec2cbda085 0.741233156000 1336240 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": 880686, "vin": [ { "gen": { "height": 880676 } } ], "vout": [ { "amount": 741233156, "target": { "key": "98064f2c7a61bc32e0c06790e5f2a1c2ddd7f437e7b43bab97f37bec2cbda085" } } ], "extra": [ 1, 236, 249, 210, 94, 254, 67, 38, 29, 149, 37, 244, 42, 172, 152, 224, 160, 236, 118, 91, 139, 146, 146, 244, 173, 210, 137, 243, 37, 131, 253, 213, 126, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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