Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31e8f9b262401eb11cf8203079e76f3565caa534c2d8a6408bc652b6380495fb

Tx prefix hash: 148ff4f90059c1d770a04d1680c630cdae7655d00de57802bc36756b3c16d16b
Tx public key: c7826c04e0ab4a53ad29da2ff793c635d93e5b4d2f64bea9c2ddea3b971b005a
Timestamp: 1715979009 Timestamp [UCT]: 2024-05-17 20:50:09 Age [y:d:h:m:s]: 00:237:23:07:52
Block: 1024224 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170308 RingCT/type: yes/0
Extra: 01c7826c04e0ab4a53ad29da2ff793c635d93e5b4d2f64bea9c2ddea3b971b005a02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 494487d2fa046649aefe0364ed1909af91bc9d6398f3eb6349c8d90e8955e049 0.600000000000 1489799 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": 1024234, "vin": [ { "gen": { "height": 1024224 } } ], "vout": [ { "amount": 600000000, "target": { "key": "494487d2fa046649aefe0364ed1909af91bc9d6398f3eb6349c8d90e8955e049" } } ], "extra": [ 1, 199, 130, 108, 4, 224, 171, 74, 83, 173, 41, 218, 47, 247, 147, 198, 53, 217, 62, 91, 77, 47, 100, 190, 169, 194, 221, 234, 59, 151, 27, 0, 90, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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