Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4db4ad3c267941020cde7a4e0260326f775055169b3fbc545587483c1bdd4233

Tx prefix hash: 7938a69323c7c9aaed9e1f4c0773a4b2176625202611f04a0c1ba03e181f81d9
Tx public key: 485173baa4ee00c7e544f109ed2e3eef76e2deb7a3870ee615d227a342c5010f
Timestamp: 1713338749 Timestamp [UCT]: 2024-04-17 07:25:49 Age [y:d:h:m:s]: 01:001:06:07:48
Block: 1002324 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261849 RingCT/type: yes/0
Extra: 01485173baa4ee00c7e544f109ed2e3eef76e2deb7a3870ee615d227a342c5010f0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fde55d80162e371c69ff9a7b9d4e41b69b81413841085a8dad62a7ea7d026df2 0.600000000000 1462840 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": 1002334, "vin": [ { "gen": { "height": 1002324 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fde55d80162e371c69ff9a7b9d4e41b69b81413841085a8dad62a7ea7d026df2" } } ], "extra": [ 1, 72, 81, 115, 186, 164, 238, 0, 199, 229, 68, 241, 9, 237, 46, 62, 239, 118, 226, 222, 183, 163, 135, 14, 230, 21, 210, 39, 163, 66, 197, 1, 15, 2, 17, 0, 0, 0, 2, 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