Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bf690bc32976bbf88a4387782b982281269018e51d91241580ad53769e473e0

Tx prefix hash: fa6b084a154fcbae7e9ced16c87dff5119253d00efcec1dc035e6216d54a0766
Tx public key: 7de49bad0cd726b9c3132ee3a86f68b1a9080b54b86e7924e7eb9a843fd15664
Timestamp: 1745287350 Timestamp [UCT]: 2025-04-22 02:02:30 Age [y:d:h:m:s]: 00:041:20:49:49
Block: 1266682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29966 RingCT/type: yes/0
Extra: 017de49bad0cd726b9c3132ee3a86f68b1a9080b54b86e7924e7eb9a843fd156640211000000046c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 857dd4ab7dc911b6ae8c83f1e080de1eb834e7ab8dbf72d017738165b5ffe0d8 0.600000000000 1753903 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": 1266692, "vin": [ { "gen": { "height": 1266682 } } ], "vout": [ { "amount": 600000000, "target": { "key": "857dd4ab7dc911b6ae8c83f1e080de1eb834e7ab8dbf72d017738165b5ffe0d8" } } ], "extra": [ 1, 125, 228, 155, 173, 12, 215, 38, 185, 195, 19, 46, 227, 168, 111, 104, 177, 169, 8, 11, 84, 184, 110, 121, 36, 231, 235, 154, 132, 63, 209, 86, 100, 2, 17, 0, 0, 0, 4, 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