Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 833c942ae1ef427efa73a1f307938d95e77f179527a6c952b83c31f2c6d19911

Tx prefix hash: 2cfe2fc2b8d4295b6b6f027370cd27313a9c7ee6f0b1b40167c94ed05ce50d1a
Tx public key: e24d16ee45b588eed9e07a16f6a4fb924bdf8f93c6cfe5fdcefd74cc4649fa65
Timestamp: 1712037244 Timestamp [UCT]: 2024-04-02 05:54:04 Age [y:d:h:m:s]: 01:218:07:51:32
Block: 991512 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 414720 RingCT/type: yes/0
Extra: 01e24d16ee45b588eed9e07a16f6a4fb924bdf8f93c6cfe5fdcefd74cc4649fa650211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78806a4928cc247974ad44ea42c703ab51f562e6e98f7e1ef6ad514aacb119ba 0.600000000000 1451848 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": 991522, "vin": [ { "gen": { "height": 991512 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78806a4928cc247974ad44ea42c703ab51f562e6e98f7e1ef6ad514aacb119ba" } } ], "extra": [ 1, 226, 77, 22, 238, 69, 181, 136, 238, 217, 224, 122, 22, 246, 164, 251, 146, 75, 223, 143, 147, 198, 207, 229, 253, 206, 253, 116, 204, 70, 73, 250, 101, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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