Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a06970fa09d50a4ee77493f1ed8798254e1b1ad7a58988d55976a40e68f45ca4

Tx prefix hash: f4ef28860cc2e3418ffd9758bf1f7492b675c6830b808ae614d3b7102fe3b63d
Tx public key: 634d79e8c7a1539a3d8e322774c50c35e3721cdac16041e98bc0e7800ba43aae
Timestamp: 1708955957 Timestamp [UCT]: 2024-02-26 13:59:17 Age [y:d:h:m:s]: 01:088:08:35:11
Block: 966002 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324195 RingCT/type: yes/0
Extra: 01634d79e8c7a1539a3d8e322774c50c35e3721cdac16041e98bc0e7800ba43aae0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51f2580bd60b17e7c6bbfee1338c99fb732b0471975410cf4b58a3bc260f3763 0.600000000000 1425757 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": 966012, "vin": [ { "gen": { "height": 966002 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51f2580bd60b17e7c6bbfee1338c99fb732b0471975410cf4b58a3bc260f3763" } } ], "extra": [ 1, 99, 77, 121, 232, 199, 161, 83, 154, 61, 142, 50, 39, 116, 197, 12, 53, 227, 114, 28, 218, 193, 96, 65, 233, 139, 192, 231, 128, 11, 164, 58, 174, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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