Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81abc1ef2aff93e7deb8b83a3e5a108d3358d6713c072c6d229b5b5afb7152b7

Tx prefix hash: 4d898c3e35a3b1bad427124a9e850c717d9763b2a146604bd298fd40ad7ff1d7
Tx public key: 7111c378045a7537e9e4b3c1f6d0f6ae7f062576080eee2d32b098a1a2b58ab2
Timestamp: 1729090266 Timestamp [UCT]: 2024-10-16 14:51:06 Age [y:d:h:m:s]: 00:149:00:43:40
Block: 1132937 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106276 RingCT/type: yes/0
Extra: 017111c378045a7537e9e4b3c1f6d0f6ae7f062576080eee2d32b098a1a2b58ab2021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53ef53f0802ab0912b15e30de2c3a2902695df14fe015e05a1ce0cefd60ab40a 0.600000000000 1615978 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": 1132947, "vin": [ { "gen": { "height": 1132937 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53ef53f0802ab0912b15e30de2c3a2902695df14fe015e05a1ce0cefd60ab40a" } } ], "extra": [ 1, 113, 17, 195, 120, 4, 90, 117, 55, 233, 228, 179, 193, 246, 208, 246, 174, 127, 6, 37, 118, 8, 14, 238, 45, 50, 176, 152, 161, 162, 181, 138, 178, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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