Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 994cd4aac600d67c176704a786936ebdc83161b81b3d5480044bff2912967dc2

Tx prefix hash: ae5491865872dfeae0c481c5a2dec21a2ecdbd02ea58e43920ff5ec8b8b54d3e
Tx public key: 282b73d24fe826530498e6429c400b1b58cf9e4fad069ed40e5250b4881151a1
Timestamp: 1700247357 Timestamp [UCT]: 2023-11-17 18:55:57 Age [y:d:h:m:s]: 01:203:21:53:42
Block: 893801 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 406959 RingCT/type: yes/0
Extra: 01282b73d24fe826530498e6429c400b1b58cf9e4fad069ed40e5250b4881151a102110000000533af99f4000000000000000000

1 output(s) for total of 0.670604163000 dcy

stealth address amount amount idx
00: 0f94a26cc790fb12577d9a350a6e96cb1a706cb90d02e2e44a56295d932f743e 0.670604163000 1349986 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": 893811, "vin": [ { "gen": { "height": 893801 } } ], "vout": [ { "amount": 670604163, "target": { "key": "0f94a26cc790fb12577d9a350a6e96cb1a706cb90d02e2e44a56295d932f743e" } } ], "extra": [ 1, 40, 43, 115, 210, 79, 232, 38, 83, 4, 152, 230, 66, 156, 64, 11, 27, 88, 207, 158, 79, 173, 6, 158, 212, 14, 82, 80, 180, 136, 17, 81, 161, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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