Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ee44e62ce5b914ca5c1f244dc628d87f065e8e28c5b7af682c6633e9bd3e7a2

Tx prefix hash: d0ac73cff65507eaf3eb60d2293dda002cdda3df3b6b20e464d0b3ea23ca1c54
Tx public key: dba710fd01850462f7a47bcbfd648bff00e4fd3d2093db0d554584ccd200d5a8
Timestamp: 1715352194 Timestamp [UCT]: 2024-05-10 14:43:14 Age [y:d:h:m:s]: 00:339:02:23:36
Block: 1019024 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242393 RingCT/type: yes/0
Extra: 01dba710fd01850462f7a47bcbfd648bff00e4fd3d2093db0d554584ccd200d5a80211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff80aab3414cd09132475017e5c111c2c8fcd21baaa460ed76dc0d7b320bc1ca 0.600000000000 1482881 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": 1019034, "vin": [ { "gen": { "height": 1019024 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff80aab3414cd09132475017e5c111c2c8fcd21baaa460ed76dc0d7b320bc1ca" } } ], "extra": [ 1, 219, 167, 16, 253, 1, 133, 4, 98, 247, 164, 123, 203, 253, 100, 139, 255, 0, 228, 253, 61, 32, 147, 219, 13, 85, 69, 132, 204, 210, 0, 213, 168, 2, 17, 0, 0, 0, 3, 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