Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a9a534792b1d32dd8ae356301a69ac32a5f3e3152e30668cb0382de5f66b961

Tx prefix hash: ca8680d728e360c193ed2f2aa54b1f563157dc56b87fe45a8a9cdda59ac42c67
Tx public key: 51d3a6e5d02f3c59b18b67e99c01d11c43278a44162a1f0723e62b17f661dab6
Timestamp: 1730808325 Timestamp [UCT]: 2024-11-05 12:05:25 Age [y:d:h:m:s]: 00:205:17:51:30
Block: 1147071 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146923 RingCT/type: yes/0
Extra: 0151d3a6e5d02f3c59b18b67e99c01d11c43278a44162a1f0723e62b17f661dab6021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e1429d450824f062fdc13a5d59847d98d207cba5be8e6cbcd42a144822ba5e6 0.600000000000 1631764 of 15

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": 1147081, "vin": [ { "gen": { "height": 1147071 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e1429d450824f062fdc13a5d59847d98d207cba5be8e6cbcd42a144822ba5e6" } } ], "extra": [ 1, 81, 211, 166, 229, 208, 47, 60, 89, 177, 139, 103, 233, 156, 1, 209, 28, 67, 39, 138, 68, 22, 42, 31, 7, 35, 230, 43, 23, 246, 97, 218, 182, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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