Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4041226351bc731ff4da85987027e497f5b0bd9b098f34d0f55c4c35c8b796f0

Tx prefix hash: cc80d37e76be0576d7cddcec967a42f01d6188b511f2483a7cc3b73f82332a9a
Tx public key: dcc16d7d9e1027e6f4d587952dec63af56ad8b49f243d0cc36b888ff6a246f5c
Timestamp: 1705141799 Timestamp [UCT]: 2024-01-13 10:29:59 Age [y:d:h:m:s]: 01:082:17:26:33
Block: 934357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320221 RingCT/type: yes/0
Extra: 01dcc16d7d9e1027e6f4d587952dec63af56ad8b49f243d0cc36b888ff6a246f5c0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d275227e474e8a7f0a9fecc7b6c00f14627fe82f29f46c1dce3baea56db63b7 0.600000000000 1392363 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": 934367, "vin": [ { "gen": { "height": 934357 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d275227e474e8a7f0a9fecc7b6c00f14627fe82f29f46c1dce3baea56db63b7" } } ], "extra": [ 1, 220, 193, 109, 125, 158, 16, 39, 230, 244, 213, 135, 149, 45, 236, 99, 175, 86, 173, 139, 73, 242, 67, 208, 204, 54, 184, 136, 255, 106, 36, 111, 92, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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