Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 106d5261f7610342a50a79ce4453274eeba0d222f7c18b01de7511d4180190d9

Tx prefix hash: b595ddd3ec41df455a6579399d76e393efd4fa654957011ae164c827d19d5d7a
Tx public key: 29ef77ae34d9e7b6d8df2944217e97da5d43698ba5f67b1c620bc4faa39bb7a8
Timestamp: 1721246528 Timestamp [UCT]: 2024-07-17 20:02:08 Age [y:d:h:m:s]: 00:335:06:34:12
Block: 1067903 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239454 RingCT/type: yes/0
Extra: 0129ef77ae34d9e7b6d8df2944217e97da5d43698ba5f67b1c620bc4faa39bb7a802110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf7d9623462449495b3af14f799e4eeffe89e13b4b5d19dc24b46a125cd64a08 0.600000000000 1538844 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": 1067913, "vin": [ { "gen": { "height": 1067903 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf7d9623462449495b3af14f799e4eeffe89e13b4b5d19dc24b46a125cd64a08" } } ], "extra": [ 1, 41, 239, 119, 174, 52, 217, 231, 182, 216, 223, 41, 68, 33, 126, 151, 218, 93, 67, 105, 139, 165, 246, 123, 28, 98, 11, 196, 250, 163, 155, 183, 168, 2, 17, 0, 0, 0, 2, 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