Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03ddd503be37c3b32e22c4b5658b3e59b6edf61a8c2ccbc4d949458c1e872b78

Tx prefix hash: da563f2724a8d886aa0991b07692c885dcefd9a5fe80384a138cb6c7457cebfe
Tx public key: 082e49f3146f7fbdc42495ab5f9a243e406fc22e769f0fd313c686f801eccbfa
Timestamp: 1700144129 Timestamp [UCT]: 2023-11-16 14:15:29 Age [y:d:h:m:s]: 01:150:12:41:06
Block: 892943 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368763 RingCT/type: yes/0
Extra: 01082e49f3146f7fbdc42495ab5f9a243e406fc22e769f0fd313c686f801eccbfa02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.675008367000 dcy

stealth address amount amount idx
00: b7d5009d0f212ca731ec1f90fb3874eba2f5176d9948d0ee6539c15fbe534134 0.675008367000 1349098 of 0

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": 892953, "vin": [ { "gen": { "height": 892943 } } ], "vout": [ { "amount": 675008367, "target": { "key": "b7d5009d0f212ca731ec1f90fb3874eba2f5176d9948d0ee6539c15fbe534134" } } ], "extra": [ 1, 8, 46, 73, 243, 20, 111, 127, 189, 196, 36, 149, 171, 95, 154, 36, 62, 64, 111, 194, 46, 118, 159, 15, 211, 19, 198, 134, 248, 1, 236, 203, 250, 2, 17, 0, 0, 0, 2, 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