Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b7fe533ccd7a5f0ec5786c55bf8bd77f721b88bfe22576faaaf4af2d8f3da2a

Tx prefix hash: bd18bd83293fd6ed7f46aa92b37a94cbf645801bc30a46d287df4f14e85a9a41
Tx public key: 3a28e4db7552491f3b2471890fefd96e2f6d8b231a659df0d2fa6afa9add1178
Timestamp: 1728688602 Timestamp [UCT]: 2024-10-11 23:16:42 Age [y:d:h:m:s]: 00:103:14:04:06
Block: 1129592 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74000 RingCT/type: yes/0
Extra: 013a28e4db7552491f3b2471890fefd96e2f6d8b231a659df0d2fa6afa9add1178021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f570ef30fb42dd018b8f2f4b9dec16209048365b087a38dde3d92bd7f67e9f0f 0.600000000000 1612419 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": 1129602, "vin": [ { "gen": { "height": 1129592 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f570ef30fb42dd018b8f2f4b9dec16209048365b087a38dde3d92bd7f67e9f0f" } } ], "extra": [ 1, 58, 40, 228, 219, 117, 82, 73, 31, 59, 36, 113, 137, 15, 239, 217, 110, 47, 109, 139, 35, 26, 101, 157, 240, 210, 250, 106, 250, 154, 221, 17, 120, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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