Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ee0359c7fc53799d1319f8b4e63c2fa4777fc7d371755d4b9e7bb8eae270ff9

Tx prefix hash: fbb29a4a4067b0492aaeee5ec930e4422a1a9ad033313f6dc8a8c92e7f5dbe46
Tx public key: d0d1e31e624aa5e1b73a2bb63537967bb1536ea0458cccc1960702f835a0d267
Timestamp: 1715197112 Timestamp [UCT]: 2024-05-08 19:38:32 Age [y:d:h:m:s]: 01:186:10:47:04
Block: 1017749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391862 RingCT/type: yes/0
Extra: 01d0d1e31e624aa5e1b73a2bb63537967bb1536ea0458cccc1960702f835a0d2670211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ebfcfc05dc5af753e1fa0ff5da6bdfdb3b05304d9a75515f7651450711d20ab 0.600000000000 1481534 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": 1017759, "vin": [ { "gen": { "height": 1017749 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ebfcfc05dc5af753e1fa0ff5da6bdfdb3b05304d9a75515f7651450711d20ab" } } ], "extra": [ 1, 208, 209, 227, 30, 98, 74, 165, 225, 183, 58, 43, 182, 53, 55, 150, 123, 177, 83, 110, 160, 69, 140, 204, 193, 150, 7, 2, 248, 53, 160, 210, 103, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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