Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b165418f4b5119f746f71c9493afcad2b2b197012f5eaa8b7eba8f56f04a3a5

Tx prefix hash: 174b4fe25ec28d8aa6319541e3c0069248ff8a4e8773e2c91bff027c9727839d
Tx public key: dd8fd6c4305463e80c5dc5236a9d33b19ec788b22b258248a1c24795beaf9ead
Timestamp: 1693996158 Timestamp [UCT]: 2023-09-06 10:29:18 Age [y:d:h:m:s]: 01:070:22:25:21
Block: 842151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311986 RingCT/type: yes/0
Extra: 01dd8fd6c4305463e80c5dc5236a9d33b19ec788b22b258248a1c24795beaf9ead02110000000dfaf35c9c000000000000000000

1 output(s) for total of 0.994498681000 dcy

stealth address amount amount idx
00: a877964e27a713d4cd4e505a77e719e5d013f0276be41e1e25c8e3541844b430 0.994498681000 1295245 of 0

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": 842161, "vin": [ { "gen": { "height": 842151 } } ], "vout": [ { "amount": 994498681, "target": { "key": "a877964e27a713d4cd4e505a77e719e5d013f0276be41e1e25c8e3541844b430" } } ], "extra": [ 1, 221, 143, 214, 196, 48, 84, 99, 232, 12, 93, 197, 35, 106, 157, 51, 177, 158, 199, 136, 178, 43, 37, 130, 72, 161, 194, 71, 149, 190, 175, 158, 173, 2, 17, 0, 0, 0, 13, 250, 243, 92, 156, 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