Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ac54e15263855272e4148a3b21fb155376c11485a2cce987bd6fc01bff24af2

Tx prefix hash: bee22c77347ce534e6c811f761d7d2e46bb51302a373575bc82267e1182bc8c9
Tx public key: 603de74a46d9f16d13984f61419ae4b5c0d0fa7e6290a043ef453bc5c8a898b2
Timestamp: 1713721307 Timestamp [UCT]: 2024-04-21 17:41:47 Age [y:d:h:m:s]: 00:310:03:46:41
Block: 1005493 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221716 RingCT/type: yes/0
Extra: 01603de74a46d9f16d13984f61419ae4b5c0d0fa7e6290a043ef453bc5c8a898b20211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3b982127bc2e3efce51e87492b21776574ef79f16c217d057b26a0ab64c1b6a 0.600000000000 1466205 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": 1005503, "vin": [ { "gen": { "height": 1005493 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3b982127bc2e3efce51e87492b21776574ef79f16c217d057b26a0ab64c1b6a" } } ], "extra": [ 1, 96, 61, 231, 74, 70, 217, 241, 109, 19, 152, 79, 97, 65, 154, 228, 181, 192, 208, 250, 126, 98, 144, 160, 67, 239, 69, 59, 197, 200, 168, 152, 178, 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