Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f583b32a93739afcd4fa68b6621a2f53507617eeb581bd8b5b789ca7a7a7e33f

Tx prefix hash: 0baf2ad04ee0d79d09de936ef63e8719898358f9380dd0655b8bd463acfa26f0
Tx public key: 1f84856c5dbf3153b41ca40cf86219fe8ae13c7734c01118a85f9f3287a956d7
Timestamp: 1582521272 Timestamp [UCT]: 2020-02-24 05:14:32 Age [y:d:h:m:s]: 04:351:23:27:41
Block: 71546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1143733 RingCT/type: yes/0
Extra: 011f84856c5dbf3153b41ca40cf86219fe8ae13c7734c01118a85f9f3287a956d702110000000156c366d3000000000000000000

1 output(s) for total of 355.581537341000 dcy

stealth address amount amount idx
00: db5d52ebbe677357bc23e3a66d7ee809ab7c93e1eee1d50e61c19bfade17c4d6 355.581537341000 132109 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": 71556, "vin": [ { "gen": { "height": 71546 } } ], "vout": [ { "amount": 355581537341, "target": { "key": "db5d52ebbe677357bc23e3a66d7ee809ab7c93e1eee1d50e61c19bfade17c4d6" } } ], "extra": [ 1, 31, 132, 133, 108, 93, 191, 49, 83, 180, 28, 164, 12, 248, 98, 25, 254, 138, 225, 60, 119, 52, 192, 17, 24, 168, 95, 159, 50, 135, 169, 86, 215, 2, 17, 0, 0, 0, 1, 86, 195, 102, 211, 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