Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7440271fc31848a3c2c2bb0c1edf1224aec22830535734f64b4ba288b1f6f719

Tx prefix hash: 9f8074a4c46cfeb501c2f77174c98e58558178ac61731807ed579d1eb170bc14
Tx public key: b32baf591daea4e58cd9d61e674933325bdac72824d74f9974613da4df9c6987
Timestamp: 1699029396 Timestamp [UCT]: 2023-11-03 16:36:36 Age [y:d:h:m:s]: 01:079:02:18:44
Block: 883907 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317707 RingCT/type: yes/0
Extra: 01b32baf591daea4e58cd9d61e674933325bdac72824d74f9974613da4df9c698702110000000875e3f0e9000000000000000000

1 output(s) for total of 0.723184632000 dcy

stealth address amount amount idx
00: d1f4481e99c0c9fd901ce4de6b18e4427040ed564482d371de8ce4a7a9c289a1 0.723184632000 1339632 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": 883917, "vin": [ { "gen": { "height": 883907 } } ], "vout": [ { "amount": 723184632, "target": { "key": "d1f4481e99c0c9fd901ce4de6b18e4427040ed564482d371de8ce4a7a9c289a1" } } ], "extra": [ 1, 179, 43, 175, 89, 29, 174, 164, 229, 140, 217, 214, 30, 103, 73, 51, 50, 91, 218, 199, 40, 36, 215, 79, 153, 116, 97, 61, 164, 223, 156, 105, 135, 2, 17, 0, 0, 0, 8, 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