Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 859de24f05822618afc03b4d8caaee592959f41837b9cb9f93ffa37a322037a9

Tx prefix hash: 887a0feacaeed46544e802813f5107a48664d54dcfa5deb605d020a55795080c
Tx public key: a0cbb4ca01d158cc9ba2ddeb3aa6fd15ff9f083e9137b018a0f4e128ecc99b7c
Timestamp: 1730425174 Timestamp [UCT]: 2024-11-01 01:39:34 Age [y:d:h:m:s]: 00:227:09:45:13
Block: 1143913 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162294 RingCT/type: yes/0
Extra: 01a0cbb4ca01d158cc9ba2ddeb3aa6fd15ff9f083e9137b018a0f4e128ecc99b7c021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 064f75ea8f5eda8b0d6424fb67cfb09b93c805f4da2bbff6cc2ac94bcf9f58cf 0.600000000000 1627946 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": 1143923, "vin": [ { "gen": { "height": 1143913 } } ], "vout": [ { "amount": 600000000, "target": { "key": "064f75ea8f5eda8b0d6424fb67cfb09b93c805f4da2bbff6cc2ac94bcf9f58cf" } } ], "extra": [ 1, 160, 203, 180, 202, 1, 209, 88, 204, 155, 162, 221, 235, 58, 166, 253, 21, 255, 159, 8, 62, 145, 55, 176, 24, 160, 244, 225, 40, 236, 201, 155, 124, 2, 17, 0, 0, 0, 4, 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