Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 571bbcf6c3c62a413a02d887543cb848d44248847330b4ecde07e3df9b7c09f7

Tx prefix hash: 2e17107f4dcce4a3120a6026ece49e112f4bc72d702f3158b80aa21c34a7815d
Tx public key: 9e6ddd49b19bc7d828993f18344ff2452be90ccc2f2c4fb03100529809e53315
Timestamp: 1698442432 Timestamp [UCT]: 2023-10-27 21:33:52 Age [y:d:h:m:s]: 02:008:04:53:51
Block: 879040 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 525439 RingCT/type: yes/0
Extra: 019e6ddd49b19bc7d828993f18344ff2452be90ccc2f2c4fb03100529809e5331502110000000533af99f4000000000000000000

1 output(s) for total of 0.750543015000 dcy

stealth address amount amount idx
00: ca717b53548afc503237bd80890d27387973dc811b8b6a09c78cb364c4ea184c 0.750543015000 1334538 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": 879050, "vin": [ { "gen": { "height": 879040 } } ], "vout": [ { "amount": 750543015, "target": { "key": "ca717b53548afc503237bd80890d27387973dc811b8b6a09c78cb364c4ea184c" } } ], "extra": [ 1, 158, 109, 221, 73, 177, 155, 199, 216, 40, 153, 63, 24, 52, 79, 242, 69, 43, 233, 12, 204, 47, 44, 79, 176, 49, 0, 82, 152, 9, 229, 51, 21, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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