Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 946a5ace797f9dad496608ae004baa47439b258df4cd0f5fd2485338118eeb61

Tx prefix hash: 66b4e4909c43b7b4a971dddcd8ea8bffbe6107dd1bcbc5dabb2e90abe814bc02
Tx public key: 36af5bac68a24fe9accdd9bcb1d5ab8a2181b96ec6d9c02fca1fb36e3abea05f
Timestamp: 1719639013 Timestamp [UCT]: 2024-06-29 05:30:13 Age [y:d:h:m:s]: 00:344:22:27:09
Block: 1054560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246537 RingCT/type: yes/0
Extra: 0136af5bac68a24fe9accdd9bcb1d5ab8a2181b96ec6d9c02fca1fb36e3abea05f02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d35681d47eba69870985f5e48b505c90dec3446937d6c0ba66b18bfcf056cb96 0.600000000000 1524923 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": 1054570, "vin": [ { "gen": { "height": 1054560 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d35681d47eba69870985f5e48b505c90dec3446937d6c0ba66b18bfcf056cb96" } } ], "extra": [ 1, 54, 175, 91, 172, 104, 162, 79, 233, 172, 205, 217, 188, 177, 213, 171, 138, 33, 129, 185, 110, 198, 217, 192, 47, 202, 31, 179, 110, 58, 190, 160, 95, 2, 17, 0, 0, 0, 3, 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