Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aea1e1ce32b8fb72676bbdf406d085443e0d5b6974c3f640b0e8293c21369873

Tx prefix hash: ba9dc16771ebfdce144aeb2b0c3b9111dbddf8b37394012c31b4d335619a3551
Tx public key: f0f29f40b649e603bcd8af953e49a0bbebf1f21875063c20b9b5c9e5f4024490
Timestamp: 1736322093 Timestamp [UCT]: 2025-01-08 07:41:33 Age [y:d:h:m:s]: 00:296:04:25:56
Block: 1192736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209179 RingCT/type: yes/0
Extra: 01f0f29f40b649e603bcd8af953e49a0bbebf1f21875063c20b9b5c9e5f40244900211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ab0777d1c193523b095c685bebecbfa294002941b9957d1cbf92cdfef51770c 0.600000000000 1679291 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": 1192746, "vin": [ { "gen": { "height": 1192736 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ab0777d1c193523b095c685bebecbfa294002941b9957d1cbf92cdfef51770c" } } ], "extra": [ 1, 240, 242, 159, 64, 182, 73, 230, 3, 188, 216, 175, 149, 62, 73, 160, 187, 235, 241, 242, 24, 117, 6, 60, 32, 185, 181, 201, 229, 244, 2, 68, 144, 2, 17, 0, 0, 0, 5, 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