Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 388501562bba1ea6b15a634cc5eeae549c4db4548add1fd5353d5c66d2827139

Tx prefix hash: e4df1b3904e5ac9d7dcc6de6df1ce0f6fe0715fda51ae4c9e4926a9c378239f8
Tx public key: 2107e5359bcc4b60687fcba4e799853c7b07a5cea4af2aefcbd3d50ebcd2f971
Timestamp: 1736826203 Timestamp [UCT]: 2025-01-14 03:43:23 Age [y:d:h:m:s]: 00:158:04:13:09
Block: 1196910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112701 RingCT/type: yes/0
Extra: 012107e5359bcc4b60687fcba4e799853c7b07a5cea4af2aefcbd3d50ebcd2f9710211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38d3c12c94ed1b2808ede0c13b84bf73f4dd09090eb789c6aca6e906bdf44d14 0.600000000000 1683515 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": 1196920, "vin": [ { "gen": { "height": 1196910 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38d3c12c94ed1b2808ede0c13b84bf73f4dd09090eb789c6aca6e906bdf44d14" } } ], "extra": [ 1, 33, 7, 229, 53, 155, 204, 75, 96, 104, 127, 203, 164, 231, 153, 133, 60, 123, 7, 165, 206, 164, 175, 42, 239, 203, 211, 213, 14, 188, 210, 249, 113, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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