Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 139fbc9bb093abb9e60947a6e00c4f5783e13a98d981f4f6e106d391ee2766c9

Tx prefix hash: a06ef4668e831e1eaafb001a7509967c53aab62603e89470df68246256c3c961
Tx public key: 5afe2f341a49bbafdc31092594bc7d46fd2b2fb344a29aac0f5506e20d03099d
Timestamp: 1702323505 Timestamp [UCT]: 2023-12-11 19:38:25 Age [y:d:h:m:s]: 01:340:10:53:19
Block: 911014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 502185 RingCT/type: yes/0
Extra: 015afe2f341a49bbafdc31092594bc7d46fd2b2fb344a29aac0f5506e20d03099d02110000000675e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc592eb1e5a85f31171db8b967d6d77e06441c997872c70cc8be5f6799a1aab3 0.600000000000 1368189 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": 911024, "vin": [ { "gen": { "height": 911014 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc592eb1e5a85f31171db8b967d6d77e06441c997872c70cc8be5f6799a1aab3" } } ], "extra": [ 1, 90, 254, 47, 52, 26, 73, 187, 175, 220, 49, 9, 37, 148, 188, 125, 70, 253, 43, 47, 179, 68, 162, 154, 172, 15, 85, 6, 226, 13, 3, 9, 157, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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