Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3dd2e8e1bf67b6ddc157083c5dc3fa1db2d8b06a2677a8fb5f8ae74fe9de85fc

Tx prefix hash: c981356fe9658e3895f4e9de96f984da2ead69074257907579cf02791f456c73
Tx public key: f1ae8ede9f60f7c099c25747827c01bc02933d47274ff38b607de83152f0809a
Timestamp: 1752910082 Timestamp [UCT]: 2025-07-19 07:28:02 Age [y:d:h:m:s]: 00:163:22:41:14
Block: 1328672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116016 RingCT/type: yes/0
Extra: 01f1ae8ede9f60f7c099c25747827c01bc02933d47274ff38b607de83152f0809a021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0d14c2b09e208c88f11a5b70d71dc29cbe2f61e05051a7aa66323eb3bda22b7 0.600000000000 1816435 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": 1328682, "vin": [ { "gen": { "height": 1328672 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0d14c2b09e208c88f11a5b70d71dc29cbe2f61e05051a7aa66323eb3bda22b7" } } ], "extra": [ 1, 241, 174, 142, 222, 159, 96, 247, 192, 153, 194, 87, 71, 130, 124, 1, 188, 2, 147, 61, 71, 39, 79, 243, 139, 96, 125, 232, 49, 82, 240, 128, 154, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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