Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 160f164736f767fe1ba1bcc2266cf84130f87b15440e0e40c8d53d01f2b9d450

Tx prefix hash: 706f28a70ae2ed07804cfe378b0e45c201f8c442077317e1e8564349bd56b15f
Tx public key: b1577be64f9b8937c6a4d38bba4fbf1c6bedcc64ca8af29e836d1331364eeb6e
Timestamp: 1711586855 Timestamp [UCT]: 2024-03-28 00:47:35 Age [y:d:h:m:s]: 00:301:23:49:54
Block: 987826 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216105 RingCT/type: yes/0
Extra: 01b1577be64f9b8937c6a4d38bba4fbf1c6bedcc64ca8af29e836d1331364eeb6e0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4aebd9d13a840e72d7b11a2b9d7859863ddcba363b8bf0fab9bb0da1e1ceca54 0.600000000000 1448085 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": 987836, "vin": [ { "gen": { "height": 987826 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4aebd9d13a840e72d7b11a2b9d7859863ddcba363b8bf0fab9bb0da1e1ceca54" } } ], "extra": [ 1, 177, 87, 123, 230, 79, 155, 137, 55, 198, 164, 211, 139, 186, 79, 191, 28, 107, 237, 204, 100, 202, 138, 242, 158, 131, 109, 19, 49, 54, 78, 235, 110, 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