Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95ee3ec05f27c7cbbc389bc1853dacf79e69d637a4d34f5856f1b64e2a6b306c

Tx prefix hash: fb9e6dfcdf17ce790735eaeaf502b6a2d8f21a3a91030dca20540dc57d9ef5fc
Tx public key: db626a203ebb39fbffa04fa7189cd5b152dd1e311ade3f5983379d684057a9b0
Timestamp: 1744559410 Timestamp [UCT]: 2025-04-13 15:50:10 Age [y:d:h:m:s]: 00:270:14:09:52
Block: 1260672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191178 RingCT/type: yes/0
Extra: 01db626a203ebb39fbffa04fa7189cd5b152dd1e311ade3f5983379d684057a9b00211000000026c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a0e293aa9a6df2c4331a94b43f66d76010a6e233098d0a2b2e0e3fe863cffe5 0.600000000000 1747833 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": 1260682, "vin": [ { "gen": { "height": 1260672 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a0e293aa9a6df2c4331a94b43f66d76010a6e233098d0a2b2e0e3fe863cffe5" } } ], "extra": [ 1, 219, 98, 106, 32, 62, 187, 57, 251, 255, 160, 79, 167, 24, 156, 213, 177, 82, 221, 30, 49, 26, 222, 63, 89, 131, 55, 157, 104, 64, 87, 169, 176, 2, 17, 0, 0, 0, 2, 108, 152, 170, 61, 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