Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f49064fa843beb63e544925254f9f469fcd8102dbc6e606b548969274c4846e

Tx prefix hash: 7a85bed06868691856875eaa52ea0c2baeb2af56b3f11347b226f3abc4e1940b
Tx public key: d167f4f1522dc950c9ea235aedccf2bbd917f3d2b4e3e0568bfafabfa17329b3
Timestamp: 1709455483 Timestamp [UCT]: 2024-03-03 08:44:43 Age [y:d:h:m:s]: 01:107:02:25:31
Block: 970139 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337477 RingCT/type: yes/0
Extra: 01d167f4f1522dc950c9ea235aedccf2bbd917f3d2b4e3e0568bfafabfa17329b30211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0964279019dfaf6a265b4112cbc21dc2a2c756f4f42007a51b012704d3e1cb34 0.600000000000 1429988 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": 970149, "vin": [ { "gen": { "height": 970139 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0964279019dfaf6a265b4112cbc21dc2a2c756f4f42007a51b012704d3e1cb34" } } ], "extra": [ 1, 209, 103, 244, 241, 82, 45, 201, 80, 201, 234, 35, 90, 237, 204, 242, 187, 217, 23, 243, 210, 180, 227, 224, 86, 139, 250, 250, 191, 161, 115, 41, 179, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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