Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6ffe582b128d6c48808a44e1085f4936b2af6293990f576dded6a68c67f0f8d

Tx prefix hash: 1fee3c455dbb8dab3d51466f806901111aaf6ed38bb2b5c680068a6029b89cc6
Tx public key: b0f0a77d21067a156f4bd4ed485414227606f3a4d907acc93f6a4b6e2fb8fc77
Timestamp: 1764715709 Timestamp [UCT]: 2025-12-02 22:48:29 Age [y:d:h:m:s]: 00:004:11:07:45
Block: 1425145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3191 RingCT/type: yes/0
Extra: 01b0f0a77d21067a156f4bd4ed485414227606f3a4d907acc93f6a4b6e2fb8fc770211000000034e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d2c6cfd93ea7c34003fc0e3e732fcb9737121b3eb166d1ed36cf5024f28fa513 0.600000000000 1913778 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": 1425155, "vin": [ { "gen": { "height": 1425145 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d2c6cfd93ea7c34003fc0e3e732fcb9737121b3eb166d1ed36cf5024f28fa513" } } ], "extra": [ 1, 176, 240, 167, 125, 33, 6, 122, 21, 111, 75, 212, 237, 72, 84, 20, 34, 118, 6, 243, 164, 217, 7, 172, 201, 63, 106, 75, 110, 47, 184, 252, 119, 2, 17, 0, 0, 0, 3, 78, 123, 252, 9, 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