Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 515dc4e65d12c9f9e123d2855d7549d711a912feeb2b17e6db1a6eff7d0e4c4d

Tx prefix hash: 225ef209a9e74567c72495983c2f93c506995af3c4ba258902ecd80c9f4ccd96
Tx public key: d8c9c542336f1f2f205c06bcdcbc2f6f381e7314a62b4b1c3fe85ed912dc8e60
Timestamp: 1725814153 Timestamp [UCT]: 2024-09-08 16:49:13 Age [y:d:h:m:s]: 00:188:21:52:57
Block: 1105762 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134864 RingCT/type: yes/0
Extra: 01d8c9c542336f1f2f205c06bcdcbc2f6f381e7314a62b4b1c3fe85ed912dc8e60021100000015e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c661629c949b5736e81034fa1d2aa421e6cdbff0f3ebd4316a43273b78152e4d 0.600000000000 1583211 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": 1105772, "vin": [ { "gen": { "height": 1105762 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c661629c949b5736e81034fa1d2aa421e6cdbff0f3ebd4316a43273b78152e4d" } } ], "extra": [ 1, 216, 201, 197, 66, 51, 111, 31, 47, 32, 92, 6, 188, 220, 188, 47, 111, 56, 30, 115, 20, 166, 43, 75, 28, 63, 232, 94, 217, 18, 220, 142, 96, 2, 17, 0, 0, 0, 21, 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