Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62b7d3ab3c88ae4e79c10b48501b23cae02f028cc131361a66d8238510a20c70

Tx prefix hash: d69ce401a7f31d5a679cdf960daa3ad4ad12adc2d835eac9734c61bdd29da1ce
Tx public key: 1133e8a3d917fda947b7096b2b5cc6f277ab06c750b3f046eb8d3168d13f8abc
Timestamp: 1681984113 Timestamp [UCT]: 2023-04-20 09:48:33 Age [y:d:h:m:s]: 01:357:09:33:16
Block: 742626 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 516715 RingCT/type: yes/0
Extra: 011133e8a3d917fda947b7096b2b5cc6f277ab06c750b3f046eb8d3168d13f8abc02110000000375e3f0e9000000000000000000

1 output(s) for total of 2.125063917000 dcy

stealth address amount amount idx
00: 62957df8ec748c1c712287d8f598c9d2abfe59d97dc9bb5ec296027b6e716b56 2.125063917000 1189601 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": 742636, "vin": [ { "gen": { "height": 742626 } } ], "vout": [ { "amount": 2125063917, "target": { "key": "62957df8ec748c1c712287d8f598c9d2abfe59d97dc9bb5ec296027b6e716b56" } } ], "extra": [ 1, 17, 51, 232, 163, 217, 23, 253, 169, 71, 183, 9, 107, 43, 92, 198, 242, 119, 171, 6, 199, 80, 179, 240, 70, 235, 141, 49, 104, 209, 63, 138, 188, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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