Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed4453a35aa85b971f98e8d9cf6fcc631da7131165b6d579dc8d44e6bc8ce01d

Tx prefix hash: d1ca99d2df5b447452521ddb6d070df92f2e3581b18abf000efcf49529fa2e62
Tx public key: a53a7e96ce77dde9f9a8ea67f93fb08335ebe6a5c07604abca60474225dc1971
Timestamp: 1722634899 Timestamp [UCT]: 2024-08-02 21:41:39 Age [y:d:h:m:s]: 01:093:10:25:10
Block: 1079395 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325261 RingCT/type: yes/0
Extra: 01a53a7e96ce77dde9f9a8ea67f93fb08335ebe6a5c07604abca60474225dc197102110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 207e64c5ea076bc7cc7713b4135218e90f4d2ce9eaa088c13bb635e7c4bba21c 0.600000000000 1552334 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": 1079405, "vin": [ { "gen": { "height": 1079395 } } ], "vout": [ { "amount": 600000000, "target": { "key": "207e64c5ea076bc7cc7713b4135218e90f4d2ce9eaa088c13bb635e7c4bba21c" } } ], "extra": [ 1, 165, 58, 126, 150, 206, 119, 221, 233, 249, 168, 234, 103, 249, 63, 176, 131, 53, 235, 230, 165, 192, 118, 4, 171, 202, 96, 71, 66, 37, 220, 25, 113, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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