Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4fff9337d3841bc4984e2db3d7a051233c720bd0fb5a87067e1c5ab5017f4f3

Tx prefix hash: ecc0dde3a9289882a599f33c832cd9ce9f56c212833d027e16fa94a13e3399d6
Tx public key: 9aa37fb419c8cb5fe5f46d2a405b0232cf228cf0c0abff5d3fefca121cd6cc4f
Timestamp: 1674444007 Timestamp [UCT]: 2023-01-23 03:20:07 Age [y:d:h:m:s]: 01:354:09:46:57
Block: 680745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 514293 RingCT/type: yes/0
Extra: 019aa37fb419c8cb5fe5f46d2a405b0232cf228cf0c0abff5d3fefca121cd6cc4f0211000000015029cbac000000000000000000

1 output(s) for total of 3.407290527000 dcy

stealth address amount amount idx
00: 2c7944185359654f4fb927751c2e6321df856b5bda7899498e7f53de3e09cb4b 3.407290527000 1122806 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": 680755, "vin": [ { "gen": { "height": 680745 } } ], "vout": [ { "amount": 3407290527, "target": { "key": "2c7944185359654f4fb927751c2e6321df856b5bda7899498e7f53de3e09cb4b" } } ], "extra": [ 1, 154, 163, 127, 180, 25, 200, 203, 95, 229, 244, 109, 42, 64, 91, 2, 50, 207, 34, 140, 240, 192, 171, 255, 93, 63, 239, 202, 18, 28, 214, 204, 79, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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