Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e53f1f1b3eed5f4b1d9914f3e9ce4172f3e5056d70c56763617cd122dbf7f676

Tx prefix hash: 54ee86e7b10e4d20b09e5650cc23498b8367acb0088e462e4910488207dc4321
Tx public key: 50ee44604912b4f15ac734855c227c3957e6f067c37cfb81c3c78a6a507c6e37
Timestamp: 1723059550 Timestamp [UCT]: 2024-08-07 19:39:10 Age [y:d:h:m:s]: 01:094:11:32:47
Block: 1082914 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326011 RingCT/type: yes/0
Extra: 0150ee44604912b4f15ac734855c227c3957e6f067c37cfb81c3c78a6a507c6e37021100000001341001ae000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38bd2e2a765294d38d94d9714b1d553a1c6ebc3d67ae6e365b4669176e7f2524 0.600000000000 1556749 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": 1082924, "vin": [ { "gen": { "height": 1082914 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38bd2e2a765294d38d94d9714b1d553a1c6ebc3d67ae6e365b4669176e7f2524" } } ], "extra": [ 1, 80, 238, 68, 96, 73, 18, 180, 241, 90, 199, 52, 133, 92, 34, 124, 57, 87, 230, 240, 103, 195, 124, 251, 129, 195, 199, 138, 106, 80, 124, 110, 55, 2, 17, 0, 0, 0, 1, 52, 16, 1, 174, 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