Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23694e0da2160641b898906604d847c0184b08186fa7b1a163aa16df14c4b904

Tx prefix hash: 5d10828c9caafb4e36df2e5bfc226bf4c0aefb186b484a048f8e8a15c7ba7c8b
Tx public key: 8861a59af8fe2df988e5bf070ae976c279f80799ded1dfbf2db47ed31e8ea576
Timestamp: 1717179061 Timestamp [UCT]: 2024-05-31 18:11:01 Age [y:d:h:m:s]: 00:305:16:47:01
Block: 1034172 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218479 RingCT/type: yes/0
Extra: 018861a59af8fe2df988e5bf070ae976c279f80799ded1dfbf2db47ed31e8ea576021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a73ae00ca9aed65ef8447016cba08262494069c92aef1fab0bf314d4b18e4c6b 0.600000000000 1502657 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": 1034182, "vin": [ { "gen": { "height": 1034172 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a73ae00ca9aed65ef8447016cba08262494069c92aef1fab0bf314d4b18e4c6b" } } ], "extra": [ 1, 136, 97, 165, 154, 248, 254, 45, 249, 136, 229, 191, 7, 10, 233, 118, 194, 121, 248, 7, 153, 222, 209, 223, 191, 45, 180, 126, 211, 30, 142, 165, 118, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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