Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: acd73894d5cbf78730e291d31920e3f6bdc067bde45faddfad670bda5b52f7e4

Tx prefix hash: 89415a51bf5e84720b2e99a78b3e5740039a5985d7d623a1eb3893c56d41c253
Tx public key: 4ee3b5f89b07b43c4eddb865cffcd5201ea0fbb4daf41ebc34a568bd5b165c68
Timestamp: 1707241649 Timestamp [UCT]: 2024-02-06 17:47:29 Age [y:d:h:m:s]: 00:343:05:53:19
Block: 951771 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245727 RingCT/type: yes/0
Extra: 014ee3b5f89b07b43c4eddb865cffcd5201ea0fbb4daf41ebc34a568bd5b165c6802110000000210a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d342bb9787b24c7dbb9c1cf47d652be24c820fd7887ab7a55f6677914d503783 0.600000000000 1410587 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": 951781, "vin": [ { "gen": { "height": 951771 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d342bb9787b24c7dbb9c1cf47d652be24c820fd7887ab7a55f6677914d503783" } } ], "extra": [ 1, 78, 227, 181, 248, 155, 7, 180, 60, 78, 221, 184, 101, 207, 252, 213, 32, 30, 160, 251, 180, 218, 244, 30, 188, 52, 165, 104, 189, 91, 22, 92, 104, 2, 17, 0, 0, 0, 2, 16, 161, 116, 143, 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