Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4667f73cdd5c5b222b7ceb3f7013df8a83937094d774cb769bb159ed64d5dd2

Tx prefix hash: b82d950bb057a0d1acd4b6e481e0f271ce7a999d7297f766c632c3a4786b67c7
Tx public key: dfa4356d7705f371778569b62f6220399064c97525bac2db9c867512e62bcd7b
Timestamp: 1625438861 Timestamp [UCT]: 2021-07-04 22:47:41 Age [y:d:h:m:s]: 03:172:08:45:12
Block: 288320 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 893004 RingCT/type: yes/0
Extra: 01dfa4356d7705f371778569b62f6220399064c97525bac2db9c867512e62bcd7b0211000000134b22f71d000000000000000000

1 output(s) for total of 68.026270255000 dcy

stealth address amount amount idx
00: 51f1014be3ddbc42c5395b22eabbcfda06c514ad515fd194f98f1f4f83a8edf3 68.026270255000 604111 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": 288330, "vin": [ { "gen": { "height": 288320 } } ], "vout": [ { "amount": 68026270255, "target": { "key": "51f1014be3ddbc42c5395b22eabbcfda06c514ad515fd194f98f1f4f83a8edf3" } } ], "extra": [ 1, 223, 164, 53, 109, 119, 5, 243, 113, 119, 133, 105, 182, 47, 98, 32, 57, 144, 100, 201, 117, 37, 186, 194, 219, 156, 134, 117, 18, 230, 43, 205, 123, 2, 17, 0, 0, 0, 19, 75, 34, 247, 29, 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