Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b5ac238275dbe3641444084d5f19a0a16d1b3d078e695c70ee5032094729862

Tx prefix hash: 3f46ac50613075c446ce6ca56c5bf2a5bf0502b01a2d4531f16c621b8ef56ba1
Tx public key: d15fce4c23909e811746b279a5c370656a6c7e8e42af9518a61a92c4cdee449a
Timestamp: 1672975046 Timestamp [UCT]: 2023-01-06 03:17:26 Age [y:d:h:m:s]: 01:294:05:07:00
Block: 668558 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 471305 RingCT/type: yes/0
Extra: 01d15fce4c23909e811746b279a5c370656a6c7e8e42af9518a61a92c4cdee449a02110000000171bd5189000000000000000000

1 output(s) for total of 3.739295387000 dcy

stealth address amount amount idx
00: c3ba3ce9c7c96bdb2a1ea05e60aebbdd200ab9a9058ec34475fa4dfecfbd880f 3.739295387000 1109809 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": 668568, "vin": [ { "gen": { "height": 668558 } } ], "vout": [ { "amount": 3739295387, "target": { "key": "c3ba3ce9c7c96bdb2a1ea05e60aebbdd200ab9a9058ec34475fa4dfecfbd880f" } } ], "extra": [ 1, 209, 95, 206, 76, 35, 144, 158, 129, 23, 70, 178, 121, 165, 195, 112, 101, 106, 108, 126, 142, 66, 175, 149, 24, 166, 26, 146, 196, 205, 238, 68, 154, 2, 17, 0, 0, 0, 1, 113, 189, 81, 137, 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