Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab1df1701f30d16d865bb776aa83312189202f9a16c1c9c31efea723bfb5d30f

Tx prefix hash: 9baaedc7d7db2bd50572baa6fc80961362e521e67aa587c188c59e663cccc317
Tx public key: aa1c12338347feaba8fae3c201ae0c00887d0480c65b3aa5cc3047da8a97ceb0
Timestamp: 1749486191 Timestamp [UCT]: 2025-06-09 16:23:11 Age [y:d:h:m:s]: 00:211:17:11:22
Block: 1301459 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149067 RingCT/type: yes/0
Extra: 01aa1c12338347feaba8fae3c201ae0c00887d0480c65b3aa5cc3047da8a97ceb002110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c3d0058b6f1f660cdc3c25e903bc8196bc96c05ec84b9e44668a426c808753b 0.600000000000 1789018 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": 1301469, "vin": [ { "gen": { "height": 1301459 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c3d0058b6f1f660cdc3c25e903bc8196bc96c05ec84b9e44668a426c808753b" } } ], "extra": [ 1, 170, 28, 18, 51, 131, 71, 254, 171, 168, 250, 227, 194, 1, 174, 12, 0, 136, 125, 4, 128, 198, 91, 58, 165, 204, 48, 71, 218, 138, 151, 206, 176, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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