Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10f18c846af502c8876b03383abc048964f170676d6d0886fed1a9a53bd752be

Tx prefix hash: 728826e126f36625401d1b30e181470d8b9c047c2be2f87b963c8b7b2dea21db
Tx public key: 764bd1d9bf3714f7265fcf9181893501e5755085e2eee5f7da377212ea261140
Timestamp: 1708698034 Timestamp [UCT]: 2024-02-23 14:20:34 Age [y:d:h:m:s]: 01:264:04:58:25
Block: 963858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 447568 RingCT/type: yes/0
Extra: 01764bd1d9bf3714f7265fcf9181893501e5755085e2eee5f7da377212ea26114002110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c2651310c4adb2fdb2b9f8896ef644f9d08e47dbc23f43a0a59736f9e6f6abf5 0.600000000000 1423585 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": 963868, "vin": [ { "gen": { "height": 963858 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2651310c4adb2fdb2b9f8896ef644f9d08e47dbc23f43a0a59736f9e6f6abf5" } } ], "extra": [ 1, 118, 75, 209, 217, 191, 55, 20, 247, 38, 95, 207, 145, 129, 137, 53, 1, 229, 117, 80, 133, 226, 238, 229, 247, 218, 55, 114, 18, 234, 38, 17, 64, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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