Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b396265fe9c816622c250399bea8d420deb7a9b90f881398a607d3872d8cd47

Tx prefix hash: 7e476cb367c77518640a07c5cb5e398f986c1456f4266ba727a4b7a3363630c7
Tx public key: c25fe59bad4c87b27e534d63e9452bb18397aef3acaed2c53b9548f94d6aa1b2
Timestamp: 1631550133 Timestamp [UCT]: 2021-09-13 16:22:13 Age [y:d:h:m:s]: 02:293:04:23:45
Block: 333040 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 724122 RingCT/type: yes/0
Extra: 01c25fe59bad4c87b27e534d63e9452bb18397aef3acaed2c53b9548f94d6aa1b202110000001afdc024ec000000000000000000

1 output(s) for total of 48.361601106000 dcy

stealth address amount amount idx
00: a706acd6f0b4b78eca856eb44a55390a75a751478abbf2b5b4d358fd7866db78 48.361601106000 687437 of 0

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": 333050, "vin": [ { "gen": { "height": 333040 } } ], "vout": [ { "amount": 48361601106, "target": { "key": "a706acd6f0b4b78eca856eb44a55390a75a751478abbf2b5b4d358fd7866db78" } } ], "extra": [ 1, 194, 95, 229, 155, 173, 76, 135, 178, 126, 83, 77, 99, 233, 69, 43, 177, 131, 151, 174, 243, 172, 174, 210, 197, 59, 149, 72, 249, 77, 106, 161, 178, 2, 17, 0, 0, 0, 26, 253, 192, 36, 236, 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