Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43a3dabf11328b862eac9cb3157b17f85684e532a61e05f30ff9d8c3ff40f854

Tx prefix hash: c4893f981f429d220538d4a3b026c8700b73bfbeead395d23b0f62940b6fa529
Tx public key: d7ad75c0a639f56c09e7dca0e5ad0cd03b7a6b63d5e85b1f6475217e2201f7d3
Timestamp: 1710196027 Timestamp [UCT]: 2024-03-11 22:27:07 Age [y:d:h:m:s]: 01:013:11:33:30
Block: 976289 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270606 RingCT/type: yes/0
Extra: 01d7ad75c0a639f56c09e7dca0e5ad0cd03b7a6b63d5e85b1f6475217e2201f7d30211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56b97620db91f23dcfa08b2ae941efeb3a4d05a9fe239917f5d855416a788a4f 0.600000000000 1436280 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": 976299, "vin": [ { "gen": { "height": 976289 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56b97620db91f23dcfa08b2ae941efeb3a4d05a9fe239917f5d855416a788a4f" } } ], "extra": [ 1, 215, 173, 117, 192, 166, 57, 245, 108, 9, 231, 220, 160, 229, 173, 12, 208, 59, 122, 107, 99, 213, 232, 91, 31, 100, 117, 33, 126, 34, 1, 247, 211, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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