Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1332e644a7d56648cf5fae62fcd9a6f174b37741a4182fb3e8a1e2be044e0176

Tx prefix hash: a41ca367f689bf5cd8032c45dcf26b6312667faf098e37a80a7c798c6a3076d1
Tx public key: 8ccf2945a75917d475290d4710f4e4ded8b9b9161a944e8018ae2a9c77cb7ab4
Timestamp: 1705423109 Timestamp [UCT]: 2024-01-16 16:38:29 Age [y:d:h:m:s]: 01:100:14:53:33
Block: 936687 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333026 RingCT/type: yes/0
Extra: 018ccf2945a75917d475290d4710f4e4ded8b9b9161a944e8018ae2a9c77cb7ab40211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b4833328e7214e6c08beeb32c1f94901c4d47bc5adfa769915aa7290574c15f 0.600000000000 1394725 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": 936697, "vin": [ { "gen": { "height": 936687 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b4833328e7214e6c08beeb32c1f94901c4d47bc5adfa769915aa7290574c15f" } } ], "extra": [ 1, 140, 207, 41, 69, 167, 89, 23, 212, 117, 41, 13, 71, 16, 244, 228, 222, 216, 185, 185, 22, 26, 148, 78, 128, 24, 174, 42, 156, 119, 203, 122, 180, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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