Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea119c23f480994d9e83c52a8299ac0ec30ee3481c0781829ff5b8fb5e950241

Tx prefix hash: 3baf9c9b16efd375d0d812aef0f4d21931fd4ea355a369457dca1433e264e7df
Tx public key: 2e4545c4c71071aa44f42cf4748b5071912383b67cac4fbdbf793d82dbb379f6
Timestamp: 1700188456 Timestamp [UCT]: 2023-11-17 02:34:16 Age [y:d:h:m:s]: 01:153:13:03:59
Block: 893301 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370937 RingCT/type: yes/0
Extra: 012e4545c4c71071aa44f42cf4748b5071912383b67cac4fbdbf793d82dbb379f602110000000175e3f0e9000000000000000000

1 output(s) for total of 0.673167210000 dcy

stealth address amount amount idx
00: 63f2208ebf000428e72c714268fbb6480157029701a2c484241e1bd98d11081b 0.673167210000 1349464 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": 893311, "vin": [ { "gen": { "height": 893301 } } ], "vout": [ { "amount": 673167210, "target": { "key": "63f2208ebf000428e72c714268fbb6480157029701a2c484241e1bd98d11081b" } } ], "extra": [ 1, 46, 69, 69, 196, 199, 16, 113, 170, 68, 244, 44, 244, 116, 139, 80, 113, 145, 35, 131, 182, 124, 172, 79, 189, 191, 121, 61, 130, 219, 179, 121, 246, 2, 17, 0, 0, 0, 1, 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