Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88810c23dbb488b88fd91fbf99ac77b5870b9461f84621e4add12b873eb61451

Tx prefix hash: 26b1f84b752c8c5c52b4752f6380570754faa6c2b744e86a40f1ed87a88c22bb
Tx public key: 7fd365bfe64f55f3743ad0409f9952c8f5f3b2c34a60d7733eec9528672486dd
Timestamp: 1754812613 Timestamp [UCT]: 2025-08-10 07:56:53 Age [y:d:h:m:s]: 00:048:10:50:02
Block: 1344011 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33744 RingCT/type: yes/0
Extra: 017fd365bfe64f55f3743ad0409f9952c8f5f3b2c34a60d7733eec9528672486dd02110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4fd8da6966a9f18b55e9e0acb616cc32f06c0b57951af21b853e4498a3c4d692 0.600000000000 1831856 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": 1344021, "vin": [ { "gen": { "height": 1344011 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4fd8da6966a9f18b55e9e0acb616cc32f06c0b57951af21b853e4498a3c4d692" } } ], "extra": [ 1, 127, 211, 101, 191, 230, 79, 85, 243, 116, 58, 208, 64, 159, 153, 82, 200, 245, 243, 178, 195, 74, 96, 215, 115, 62, 236, 149, 40, 103, 36, 134, 221, 2, 17, 0, 0, 0, 2, 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