Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b99d65ff955eadcb0e87a545d0f1b0c5d5dd46d138e052b9b73ded1fd3d58ce

Tx prefix hash: 19e7330ad5e301401fe97d7b4f8911f65e43449c123407c3e3368285ccccfd28
Tx public key: 0dcfc08b8321e441ca5c437fafc2d24bb16303f2cf867e44966f0e9626ef28a4
Timestamp: 1745748504 Timestamp [UCT]: 2025-04-27 10:08:24 Age [y:d:h:m:s]: 00:014:06:07:08
Block: 1270514 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10190 RingCT/type: yes/0
Extra: 010dcfc08b8321e441ca5c437fafc2d24bb16303f2cf867e44966f0e9626ef28a40211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7204d03b6069fa24171b059fdc7d7c45cff5c6b8e12b329b14634f8e04352b2 0.600000000000 1757757 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": 1270524, "vin": [ { "gen": { "height": 1270514 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7204d03b6069fa24171b059fdc7d7c45cff5c6b8e12b329b14634f8e04352b2" } } ], "extra": [ 1, 13, 207, 192, 139, 131, 33, 228, 65, 202, 92, 67, 127, 175, 194, 210, 75, 177, 99, 3, 242, 207, 134, 126, 68, 150, 111, 14, 150, 38, 239, 40, 164, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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