Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80ea3e961d356d2ebb4cacf38c17cb67617f4efbac8c02b14c48faeb5ed0814b

Tx prefix hash: e4e4c9612b45255f8e433dcfe6bfe2fd6c66179ae64b363f92498cdf66187f1b
Tx public key: 536f4c0ae72606bafc114cd5b766e940d17f2e53901ca1322be71d858411197a
Timestamp: 1658341647 Timestamp [UCT]: 2022-07-20 18:27:27 Age [y:d:h:m:s]: 03:103:06:24:39
Block: 548007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 853583 RingCT/type: yes/0
Extra: 01536f4c0ae72606bafc114cd5b766e940d17f2e53901ca1322be71d858411197a021100000026cb8520c2000000000000000000

1 output(s) for total of 9.380488506000 dcy

stealth address amount amount idx
00: 42a1cb2b0c3434266e2f1bb23d1612dd98fc17c1c60f9b77893bfe4d7e222d3f 9.380488506000 979212 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": 548017, "vin": [ { "gen": { "height": 548007 } } ], "vout": [ { "amount": 9380488506, "target": { "key": "42a1cb2b0c3434266e2f1bb23d1612dd98fc17c1c60f9b77893bfe4d7e222d3f" } } ], "extra": [ 1, 83, 111, 76, 10, 231, 38, 6, 186, 252, 17, 76, 213, 183, 102, 233, 64, 209, 127, 46, 83, 144, 28, 161, 50, 43, 231, 29, 133, 132, 17, 25, 122, 2, 17, 0, 0, 0, 38, 203, 133, 32, 194, 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