Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfd045eb5b0367b7b61d1f6c7b4d09a872aeda3373c3fc94b652491e2e3f3b1c

Tx prefix hash: 28172ee2ed9877641de8a8bebc3c3cb6c012689b5d3dd433f4d792078558ea7d
Tx public key: 1cc9a9b032fa0668cc9f1b351ee3bac857f54278783d376a11c303058634700b
Timestamp: 1732745050 Timestamp [UCT]: 2024-11-27 22:04:10 Age [y:d:h:m:s]: 00:204:15:36:30
Block: 1163119 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145958 RingCT/type: yes/0
Extra: 011cc9a9b032fa0668cc9f1b351ee3bac857f54278783d376a11c303058634700b0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8117cedf0389c9c8890bc9fbb30134f9fe27d025eaa154ce7b93bb80c94c3537 0.600000000000 1648784 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": 1163129, "vin": [ { "gen": { "height": 1163119 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8117cedf0389c9c8890bc9fbb30134f9fe27d025eaa154ce7b93bb80c94c3537" } } ], "extra": [ 1, 28, 201, 169, 176, 50, 250, 6, 104, 204, 159, 27, 53, 30, 227, 186, 200, 87, 245, 66, 120, 120, 61, 55, 106, 17, 195, 3, 5, 134, 52, 112, 11, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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