Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 385d44979343c1adcd087ec24c6e0279b549f3f2d1288ff3c09b00e4f5f14c82

Tx prefix hash: 5e961c61cdd3ea8a5f4f1c0997cb9b8db4d5452a4abc84a4019881e6f5b0c499
Tx public key: 9bab2423697d656359b7facb1e91e63113acdc54e98a9b288192bd3f9d2f32d4
Timestamp: 1698021029 Timestamp [UCT]: 2023-10-23 00:30:29 Age [y:d:h:m:s]: 01:160:05:05:12
Block: 875537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375518 RingCT/type: yes/0
Extra: 019bab2423697d656359b7facb1e91e63113acdc54e98a9b288192bd3f9d2f32d402110000000175e3f0e9000000000000000000

1 output(s) for total of 0.770872380000 dcy

stealth address amount amount idx
00: fa787476c327f4ab1f6d55fa8dd4aa14642d6c0cd9c3ae2f72f780e5217a2983 0.770872380000 1330795 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": 875547, "vin": [ { "gen": { "height": 875537 } } ], "vout": [ { "amount": 770872380, "target": { "key": "fa787476c327f4ab1f6d55fa8dd4aa14642d6c0cd9c3ae2f72f780e5217a2983" } } ], "extra": [ 1, 155, 171, 36, 35, 105, 125, 101, 99, 89, 183, 250, 203, 30, 145, 230, 49, 19, 172, 220, 84, 233, 138, 155, 40, 129, 146, 189, 63, 157, 47, 50, 212, 2, 17, 0, 0, 0, 1, 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