Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 393b617f4167a7d6fb2035f526add69154726869f93f64a4fb5c0b93d0f516b0

Tx prefix hash: d84fdbeb12b7a9664842e82c4f8a8f5975610b967dbc26ae509aae934e5bdb78
Tx public key: ba29f7e5ae472b64d2e2ff3c224aeed6f60fd384748d87fe1b11489c7a493dc2
Timestamp: 1719927015 Timestamp [UCT]: 2024-07-02 13:30:15 Age [y:d:h:m:s]: 00:318:06:59:06
Block: 1056951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227454 RingCT/type: yes/0
Extra: 01ba29f7e5ae472b64d2e2ff3c224aeed6f60fd384748d87fe1b11489c7a493dc20211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 538ae5fc30b79ff8c3d3f49ab253586d537249677483bfb6691687d771b74e7a 0.600000000000 1527380 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": 1056961, "vin": [ { "gen": { "height": 1056951 } } ], "vout": [ { "amount": 600000000, "target": { "key": "538ae5fc30b79ff8c3d3f49ab253586d537249677483bfb6691687d771b74e7a" } } ], "extra": [ 1, 186, 41, 247, 229, 174, 71, 43, 100, 210, 226, 255, 60, 34, 74, 238, 214, 246, 15, 211, 132, 116, 141, 135, 254, 27, 17, 72, 156, 122, 73, 61, 194, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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