Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd3e0af7b06231b3b0700036f884c757abb28512fe83ed787088e64f301f2226

Tx prefix hash: c03955c319a6c0c6dad8d1ca6ee5f112529d4f0c59c9100516bd2d13a1ca47ec
Tx public key: 68aeb788c5bd7d882f9597d4150551925b139c07791e5d5468066a1f8e68a37d
Timestamp: 1738227147 Timestamp [UCT]: 2025-01-30 08:52:27 Age [y:d:h:m:s]: 00:293:10:16:32
Block: 1208248 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207472 RingCT/type: yes/0
Extra: 0168aeb788c5bd7d882f9597d4150551925b139c07791e5d5468066a1f8e68a37d021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b09c60fdbf1d83d1c491694c8563b256d0e0b4d97318f75c219ae6f1bcaebc39 0.600000000000 1694979 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": 1208258, "vin": [ { "gen": { "height": 1208248 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b09c60fdbf1d83d1c491694c8563b256d0e0b4d97318f75c219ae6f1bcaebc39" } } ], "extra": [ 1, 104, 174, 183, 136, 197, 189, 125, 136, 47, 149, 151, 212, 21, 5, 81, 146, 91, 19, 156, 7, 121, 30, 93, 84, 104, 6, 106, 31, 142, 104, 163, 125, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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