Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e17bb0af6fd73d645e1c7f2d5f2b050f25e0ca8e4ccb368777ac6c1ef3e2a5a

Tx prefix hash: a76fc4e031a10aa58823077f5b5722b2055120c8f784aa2c4dd6769e04f63f68
Tx public key: 05423f86df41a0ab13da93aa3ac2fddbacce0c4cb55cec0e34283ecc7e5dbbd0
Timestamp: 1577957823 Timestamp [UCT]: 2020-01-02 09:37:03 Age [y:d:h:m:s]: 05:031:20:19:24
Block: 37097 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1172489 RingCT/type: yes/0
Extra: 0105423f86df41a0ab13da93aa3ac2fddbacce0c4cb55cec0e34283ecc7e5dbbd0021100000008597126dd000000000000000000

1 output(s) for total of 462.469494696000 dcy

stealth address amount amount idx
00: fcda53a6feb492a939607d1bed73f8ce04136c25e584e7a4ac50460d622112d3 462.469494696000 62903 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": 37107, "vin": [ { "gen": { "height": 37097 } } ], "vout": [ { "amount": 462469494696, "target": { "key": "fcda53a6feb492a939607d1bed73f8ce04136c25e584e7a4ac50460d622112d3" } } ], "extra": [ 1, 5, 66, 63, 134, 223, 65, 160, 171, 19, 218, 147, 170, 58, 194, 253, 219, 172, 206, 12, 76, 181, 92, 236, 14, 52, 40, 62, 204, 126, 93, 187, 208, 2, 17, 0, 0, 0, 8, 89, 113, 38, 221, 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