Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9dfb0a4877f662479f2636862a92bd6e837060c9d362d94d72e499640ca4e706

Tx prefix hash: 001c8c3faa4f7a84a9b2b792d2cdc77ee350fd71bcabc3e5c248b285051d4fb7
Tx public key: 777eba170b51a2181ab4017d76ee9a3fe65f8254a41a3b539e358d21bae17847
Timestamp: 1763774361 Timestamp [UCT]: 2025-11-22 01:19:21 Age [y:d:h:m:s]: 00:004:12:46:18
Block: 1417335 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3247 RingCT/type: yes/0
Extra: 01777eba170b51a2181ab4017d76ee9a3fe65f8254a41a3b539e358d21bae17847021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf5a082915a20d674e1af958051fb2a4f13d1eb3cb0a48bb4cf797dde136744e 0.600000000000 1905858 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": 1417345, "vin": [ { "gen": { "height": 1417335 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf5a082915a20d674e1af958051fb2a4f13d1eb3cb0a48bb4cf797dde136744e" } } ], "extra": [ 1, 119, 126, 186, 23, 11, 81, 162, 24, 26, 180, 1, 125, 118, 238, 154, 63, 230, 95, 130, 84, 164, 26, 59, 83, 158, 53, 141, 33, 186, 225, 120, 71, 2, 17, 0, 0, 0, 1, 214, 225, 157, 124, 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